Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Resurrection #87

Open
7 of 16 tasks
ebekker opened this issue Jan 26, 2018 · 2 comments
Open
7 of 16 tasks

Resurrection #87

ebekker opened this issue Jan 26, 2018 · 2 comments

Comments

@ebekker
Copy link
Collaborator

ebekker commented Jan 26, 2018 •
edited
Loading

Now that several external platform components have stabilized, it's time to move over to them and move forward:

  • Move to .NET Core/Standard 2.x:
    • TugDSC.Abstractions (formerly Tug.Base)
      • Tests
    • TugDSC.Server.Abstractions (formerly Tug.Server.Base)
    • TugDSC.Server.WebAppHost (formerly Tug.Server)
      • Tests
    • TugDSC.Client.CLIApp (formerly Tug.Client)
      • Tests
    • TugDSC.Server.FaaS.AwsLambda (formerly Tug.Server.FaaS.AwsLambda)
  • Move to PowerShell Core v6
    • TugDSC.Server.Providers.PS6Handler (replaces Tug.Server.Providers.Ps5DscHandler)
  • Rework the extension loading mechanism -- it's unnecessarily, overly complex -- move away from MEF for now.
  • Clean up the "bundling" process and release bundles for more configurations
  • Start work on Admin API endpoint and supporting client cmdlets
  • Come up with a good solution for encrypted config elements (e.g. passwords)
  • Start work on UI layer
ebekker added a commit that referenced this issue Jan 29, 2018
@ebekker
First major commit in support of #87
7a88124 
Migrated first 3 major projects over to .NET Core/Standard 2.0
- adjusted configuration handling (still some work left here)
- adjusted logging setup (still some work left here)
- added support for running as a Windows Service
- cleaned up namespace naming conventions

NOTE, unit tests have not yet been moved over.
@zfilipov
Copy link

zfilipov commented Apr 18, 2018 •
edited
Loading

All,

We are currently leveraging this product for our project. We appreciate all of your time and effort that has gone into this, it is a great pull server solution for PowerShell DSC. We are looking to update our codebase for Tug, so I was checking in to see if there is a release for .NET Core 2.0 on the horizon.

@ebekker
Copy link
Collaborator Author

ebekker commented Apr 25, 2018

It's coming -- slowly but surely.

@CodeblackNL CodeblackNL mentioned this issue Feb 1, 2019
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ebekker @zfilipov