stackforge-cli 0.1.3__tar.gz → 0.1.4__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (25) hide show
  1. {stackforge_cli-0.1.3 → stackforge_cli-0.1.4}/PKG-INFO +107 -107
  2. {stackforge_cli-0.1.3 → stackforge_cli-0.1.4}/README.md +92 -92
  3. {stackforge_cli-0.1.3 → stackforge_cli-0.1.4}/pyproject.toml +26 -26
  4. {stackforge_cli-0.1.3 → stackforge_cli-0.1.4}/setup.cfg +4 -4
  5. {stackforge_cli-0.1.3 → stackforge_cli-0.1.4}/src/stackforge/engines/dotnet/__init__.py +7 -7
  6. {stackforge_cli-0.1.3 → stackforge_cli-0.1.4}/src/stackforge/engines/dotnet/api_generator.py +313 -312
  7. {stackforge_cli-0.1.3 → stackforge_cli-0.1.4}/src/stackforge/engines/dotnet/config_generator.py +76 -76
  8. {stackforge_cli-0.1.3 → stackforge_cli-0.1.4}/src/stackforge/engines/dotnet/csproj_generator.py +82 -82
  9. {stackforge_cli-0.1.3 → stackforge_cli-0.1.4}/src/stackforge/engines/dotnet/docker_generator.py +63 -63
  10. {stackforge_cli-0.1.3 → stackforge_cli-0.1.4}/src/stackforge/engines/dotnet/git_generator.py +126 -111
  11. {stackforge_cli-0.1.3 → stackforge_cli-0.1.4}/src/stackforge/engines/dotnet/layers_generator.py +543 -543
  12. stackforge_cli-0.1.4/src/stackforge/engines/dotnet/program_generator.py +245 -0
  13. {stackforge_cli-0.1.3 → stackforge_cli-0.1.4}/src/stackforge/engines/dotnet/scaffolder.py +74 -74
  14. {stackforge_cli-0.1.3 → stackforge_cli-0.1.4}/src/stackforge/project_name.py +34 -34
  15. {stackforge_cli-0.1.3 → stackforge_cli-0.1.4}/src/stackforge/scaffold.py +90 -90
  16. {stackforge_cli-0.1.3 → stackforge_cli-0.1.4}/src/stackforge/ui.py +72 -72
  17. {stackforge_cli-0.1.3 → stackforge_cli-0.1.4}/src/stackforge/version.py +48 -48
  18. {stackforge_cli-0.1.3 → stackforge_cli-0.1.4}/src/stackforge_cli.egg-info/PKG-INFO +107 -107
  19. {stackforge_cli-0.1.3 → stackforge_cli-0.1.4}/src/stackforge_cli.egg-info/top_level.txt +0 -1
  20. stackforge_cli-0.1.3/src/stackforge/engines/dotnet/program_generator.py +0 -195
  21. {stackforge_cli-0.1.3 → stackforge_cli-0.1.4}/src/stackforge/__init__.py +0 -0
  22. {stackforge_cli-0.1.3 → stackforge_cli-0.1.4}/src/stackforge_cli.egg-info/SOURCES.txt +0 -0
  23. {stackforge_cli-0.1.3 → stackforge_cli-0.1.4}/src/stackforge_cli.egg-info/dependency_links.txt +0 -0
  24. {stackforge_cli-0.1.3 → stackforge_cli-0.1.4}/src/stackforge_cli.egg-info/entry_points.txt +0 -0
  25. {stackforge_cli-0.1.3 → stackforge_cli-0.1.4}/src/stackforge_cli.egg-info/requires.txt +0 -0
@@ -1,107 +1,107 @@
1
- Metadata-Version: 2.4
2
- Name: stackforge-cli
3
- Version: 0.1.3
4
- Summary: A CLI scaffolder for .NET Clean Architecture projects
5
- License: MIT
6
- Keywords: scaffolder,dotnet,clean-architecture,cli
7
- Classifier: Programming Language :: Python :: 3
8
- Classifier: License :: OSI Approved :: MIT License
9
- Classifier: Operating System :: OS Independent
10
- Classifier: Environment :: Console
11
- Requires-Python: >=3.10
12
- Description-Content-Type: text/markdown
13
- Requires-Dist: colorama>=0.4.6
14
-
15
- # StackForge
16
-
17
- A CLI scaffolder for .NET Clean Architecture (CQRS) projects.
18
-
19
- ## Installation
20
-
21
- ```bash
22
- pip install stackforge-cli
23
- ```
24
-
25
- ## Usage
26
-
27
- ```bash
28
- stackforge
29
- ```
30
-
31
- Then follow the prompts to scaffold a new project.
32
-
33
- ## Version and updates
34
-
35
- Check the version you have installed:
36
-
37
- ```bash
38
- stackforge --version
39
- ```
40
-
41
- Update to the latest release:
42
-
43
- ```bash
44
- pip install --upgrade stackforge-cli
45
- ```
46
-
47
- When you run `stackforge`, it checks PyPI for a newer version and prints an upgrade notice if one is available (network required; fails silently if offline).
48
-
49
- ## What it generates
50
-
51
- - .NET 10 Clean Architecture structure (API, Application, Domain, Infrastructure, Persistence)
52
- - JWT authentication with ASP.NET Identity
53
- - Swagger UI with Bearer token support
54
- - PostgreSQL with EF Core
55
- - Docker + docker-compose with healthchecks
56
- - Role and user seeders (SuperAdmin out of the box)
57
- - Git initialization on `main` with `staging` and `development` branches
58
- - GitHub Actions workflow to create `staging` and `development` on first push to `main`
59
-
60
- ## Quickstart after scaffolding
61
-
62
- 1. Open the project in VS Code or Visual Studio
63
- 2. Run: `docker-compose up --build`
64
- 3. Visit: `http://localhost:5000/swagger`
65
-
66
- ## Git workflow
67
-
68
- Each scaffolded project is initialized with three local branches:
69
-
70
- | Branch | Purpose |
71
- |---------------|----------------------------------|
72
- | `main` | Production / default branch |
73
- | `staging` | Pre-production environment |
74
- | `development` | Active development environment |
75
-
76
- A GitHub Actions workflow (`.github/workflows/sync-branches.yml`) is also included as a fallback: if you only push `main` first, it creates remote `staging` and `development` on GitHub automatically.
77
-
78
- ### Example: push to GitHub
79
-
80
- From your scaffolded project directory (e.g. `~/stackforge/MyApi`):
81
-
82
- ```bash
83
- # 1. Create a new repo on GitHub (empty, no README), then add the remote
84
- git remote add origin https://github.com/<your-user>/MyApi.git
85
-
86
- # 2. Push all branches in one go
87
- git push -u origin --all
88
- ```
89
-
90
- That publishes `main`, `staging`, and `development` in a single command and sets upstream tracking for each.
91
-
92
- ### Day-to-day branching
93
-
94
- ```bash
95
- # Work on a feature
96
- git checkout development
97
- git checkout -b feature/my-feature
98
- # ... commit changes ...
99
- git push -u origin feature/my-feature
100
-
101
- # Merge into development when ready (via PR or locally)
102
- git checkout development
103
- git merge feature/my-feature
104
- git push origin development
105
- ```
106
-
107
- Promote changes up the chain (`development` → `staging` → `main`) using pull requests or merges as your team prefers.
1
+ Metadata-Version: 2.4
2
+ Name: stackforge-cli
3
+ Version: 0.1.4
4
+ Summary: A CLI scaffolder for .NET Clean Architecture projects
5
+ License: MIT
6
+ Keywords: scaffolder,dotnet,clean-architecture,cli
7
+ Classifier: Programming Language :: Python :: 3
8
+ Classifier: License :: OSI Approved :: MIT License
9
+ Classifier: Operating System :: OS Independent
10
+ Classifier: Environment :: Console
11
+ Requires-Python: >=3.10
12
+ Description-Content-Type: text/markdown
13
+ Requires-Dist: colorama>=0.4.6
14
+
15
+ # StackForge
16
+
17
+ A CLI scaffolder for .NET Clean Architecture (CQRS) projects.
18
+
19
+ ## Installation
20
+
21
+ ```bash
22
+ pip install stackforge-cli
23
+ ```
24
+
25
+ ## Usage
26
+
27
+ ```bash
28
+ stackforge
29
+ ```
30
+
31
+ Then follow the prompts to scaffold a new project.
32
+
33
+ ## Version and updates
34
+
35
+ Check the version you have installed:
36
+
37
+ ```bash
38
+ stackforge --version
39
+ ```
40
+
41
+ Update to the latest release:
42
+
43
+ ```bash
44
+ pip install --upgrade stackforge-cli
45
+ ```
46
+
47
+ When you run `stackforge`, it checks PyPI for a newer version and prints an upgrade notice if one is available (network required; fails silently if offline).
48
+
49
+ ## What it generates
50
+
51
+ - .NET 10 Clean Architecture structure (API, Application, Domain, Infrastructure, Persistence)
52
+ - JWT authentication with ASP.NET Identity
53
+ - Swagger UI with Bearer token support
54
+ - PostgreSQL with EF Core
55
+ - Docker + docker-compose with healthchecks
56
+ - Role and user seeders (SuperAdmin out of the box)
57
+ - Git initialization on `main` with `staging` and `development` branches
58
+ - GitHub Actions workflow to create `staging` and `development` on first push to `main`
59
+
60
+ ## Quickstart after scaffolding
61
+
62
+ 1. Open the project in VS Code or Visual Studio
63
+ 2. Run: `docker-compose up --build`
64
+ 3. Visit: `http://localhost:5000/swagger`
65
+
66
+ ## Git workflow
67
+
68
+ Each scaffolded project is initialized with three local branches:
69
+
70
+ | Branch | Purpose |
71
+ |---------------|----------------------------------|
72
+ | `main` | Production / default branch |
73
+ | `staging` | Pre-production environment |
74
+ | `development` | Active development environment |
75
+
76
+ A GitHub Actions workflow (`.github/workflows/sync-branches.yml`) is also included as a fallback: if you only push `main` first, it creates remote `staging` and `development` on GitHub automatically.
77
+
78
+ ### Example: push to GitHub
79
+
80
+ From your scaffolded project directory (e.g. `~/stackforge/MyApi`):
81
+
82
+ ```bash
83
+ # 1. Create a new repo on GitHub (empty, no README), then add the remote
84
+ git remote add origin https://github.com/<your-user>/MyApi.git
85
+
86
+ # 2. Push all branches in one go
87
+ git push -u origin --all
88
+ ```
89
+
90
+ That publishes `main`, `staging`, and `development` in a single command and sets upstream tracking for each.
91
+
92
+ ### Day-to-day branching
93
+
94
+ ```bash
95
+ # Work on a feature
96
+ git checkout development
97
+ git checkout -b feature/my-feature
98
+ # ... commit changes ...
99
+ git push -u origin feature/my-feature
100
+
101
+ # Merge into development when ready (via PR or locally)
102
+ git checkout development
103
+ git merge feature/my-feature
104
+ git push origin development
105
+ ```
106
+
107
+ Promote changes up the chain (`development` → `staging` → `main`) using pull requests or merges as your team prefers.
@@ -1,93 +1,93 @@
1
- # StackForge
2
-
3
- A CLI scaffolder for .NET Clean Architecture (CQRS) projects.
4
-
5
- ## Installation
6
-
7
- ```bash
8
- pip install stackforge-cli
9
- ```
10
-
11
- ## Usage
12
-
13
- ```bash
14
- stackforge
15
- ```
16
-
17
- Then follow the prompts to scaffold a new project.
18
-
19
- ## Version and updates
20
-
21
- Check the version you have installed:
22
-
23
- ```bash
24
- stackforge --version
25
- ```
26
-
27
- Update to the latest release:
28
-
29
- ```bash
30
- pip install --upgrade stackforge-cli
31
- ```
32
-
33
- When you run `stackforge`, it checks PyPI for a newer version and prints an upgrade notice if one is available (network required; fails silently if offline).
34
-
35
- ## What it generates
36
-
37
- - .NET 10 Clean Architecture structure (API, Application, Domain, Infrastructure, Persistence)
38
- - JWT authentication with ASP.NET Identity
39
- - Swagger UI with Bearer token support
40
- - PostgreSQL with EF Core
41
- - Docker + docker-compose with healthchecks
42
- - Role and user seeders (SuperAdmin out of the box)
43
- - Git initialization on `main` with `staging` and `development` branches
44
- - GitHub Actions workflow to create `staging` and `development` on first push to `main`
45
-
46
- ## Quickstart after scaffolding
47
-
48
- 1. Open the project in VS Code or Visual Studio
49
- 2. Run: `docker-compose up --build`
50
- 3. Visit: `http://localhost:5000/swagger`
51
-
52
- ## Git workflow
53
-
54
- Each scaffolded project is initialized with three local branches:
55
-
56
- | Branch | Purpose |
57
- |---------------|----------------------------------|
58
- | `main` | Production / default branch |
59
- | `staging` | Pre-production environment |
60
- | `development` | Active development environment |
61
-
62
- A GitHub Actions workflow (`.github/workflows/sync-branches.yml`) is also included as a fallback: if you only push `main` first, it creates remote `staging` and `development` on GitHub automatically.
63
-
64
- ### Example: push to GitHub
65
-
66
- From your scaffolded project directory (e.g. `~/stackforge/MyApi`):
67
-
68
- ```bash
69
- # 1. Create a new repo on GitHub (empty, no README), then add the remote
70
- git remote add origin https://github.com/<your-user>/MyApi.git
71
-
72
- # 2. Push all branches in one go
73
- git push -u origin --all
74
- ```
75
-
76
- That publishes `main`, `staging`, and `development` in a single command and sets upstream tracking for each.
77
-
78
- ### Day-to-day branching
79
-
80
- ```bash
81
- # Work on a feature
82
- git checkout development
83
- git checkout -b feature/my-feature
84
- # ... commit changes ...
85
- git push -u origin feature/my-feature
86
-
87
- # Merge into development when ready (via PR or locally)
88
- git checkout development
89
- git merge feature/my-feature
90
- git push origin development
91
- ```
92
-
1
+ # StackForge
2
+
3
+ A CLI scaffolder for .NET Clean Architecture (CQRS) projects.
4
+
5
+ ## Installation
6
+
7
+ ```bash
8
+ pip install stackforge-cli
9
+ ```
10
+
11
+ ## Usage
12
+
13
+ ```bash
14
+ stackforge
15
+ ```
16
+
17
+ Then follow the prompts to scaffold a new project.
18
+
19
+ ## Version and updates
20
+
21
+ Check the version you have installed:
22
+
23
+ ```bash
24
+ stackforge --version
25
+ ```
26
+
27
+ Update to the latest release:
28
+
29
+ ```bash
30
+ pip install --upgrade stackforge-cli
31
+ ```
32
+
33
+ When you run `stackforge`, it checks PyPI for a newer version and prints an upgrade notice if one is available (network required; fails silently if offline).
34
+
35
+ ## What it generates
36
+
37
+ - .NET 10 Clean Architecture structure (API, Application, Domain, Infrastructure, Persistence)
38
+ - JWT authentication with ASP.NET Identity
39
+ - Swagger UI with Bearer token support
40
+ - PostgreSQL with EF Core
41
+ - Docker + docker-compose with healthchecks
42
+ - Role and user seeders (SuperAdmin out of the box)
43
+ - Git initialization on `main` with `staging` and `development` branches
44
+ - GitHub Actions workflow to create `staging` and `development` on first push to `main`
45
+
46
+ ## Quickstart after scaffolding
47
+
48
+ 1. Open the project in VS Code or Visual Studio
49
+ 2. Run: `docker-compose up --build`
50
+ 3. Visit: `http://localhost:5000/swagger`
51
+
52
+ ## Git workflow
53
+
54
+ Each scaffolded project is initialized with three local branches:
55
+
56
+ | Branch | Purpose |
57
+ |---------------|----------------------------------|
58
+ | `main` | Production / default branch |
59
+ | `staging` | Pre-production environment |
60
+ | `development` | Active development environment |
61
+
62
+ A GitHub Actions workflow (`.github/workflows/sync-branches.yml`) is also included as a fallback: if you only push `main` first, it creates remote `staging` and `development` on GitHub automatically.
63
+
64
+ ### Example: push to GitHub
65
+
66
+ From your scaffolded project directory (e.g. `~/stackforge/MyApi`):
67
+
68
+ ```bash
69
+ # 1. Create a new repo on GitHub (empty, no README), then add the remote
70
+ git remote add origin https://github.com/<your-user>/MyApi.git
71
+
72
+ # 2. Push all branches in one go
73
+ git push -u origin --all
74
+ ```
75
+
76
+ That publishes `main`, `staging`, and `development` in a single command and sets upstream tracking for each.
77
+
78
+ ### Day-to-day branching
79
+
80
+ ```bash
81
+ # Work on a feature
82
+ git checkout development
83
+ git checkout -b feature/my-feature
84
+ # ... commit changes ...
85
+ git push -u origin feature/my-feature
86
+
87
+ # Merge into development when ready (via PR or locally)
88
+ git checkout development
89
+ git merge feature/my-feature
90
+ git push origin development
91
+ ```
92
+
93
93
  Promote changes up the chain (`development` → `staging` → `main`) using pull requests or merges as your team prefers.
@@ -1,27 +1,27 @@
1
- [build-system]
2
- requires = ["setuptools>=68", "wheel"]
3
- build-backend = "setuptools.build_meta"
4
-
5
- [project]
6
- name = "stackforge-cli"
7
- version = "0.1.3"
8
- description = "A CLI scaffolder for .NET Clean Architecture projects"
9
- readme = "README.md"
10
- requires-python = ">=3.10"
11
- license = { text = "MIT" }
12
- keywords = ["scaffolder", "dotnet", "clean-architecture", "cli"]
13
- classifiers = [
14
- "Programming Language :: Python :: 3",
15
- "License :: OSI Approved :: MIT License",
16
- "Operating System :: OS Independent",
17
- "Environment :: Console",
18
- ]
19
- dependencies = [
20
- "colorama>=0.4.6",
21
- ]
22
-
23
- [project.scripts]
24
- stackforge = "stackforge.scaffold:main"
25
-
26
- [tool.setuptools.packages.find]
1
+ [build-system]
2
+ requires = ["setuptools>=68", "wheel"]
3
+ build-backend = "setuptools.build_meta"
4
+
5
+ [project]
6
+ name = "stackforge-cli"
7
+ version = "0.1.4"
8
+ description = "A CLI scaffolder for .NET Clean Architecture projects"
9
+ readme = "README.md"
10
+ requires-python = ">=3.10"
11
+ license = { text = "MIT" }
12
+ keywords = ["scaffolder", "dotnet", "clean-architecture", "cli"]
13
+ classifiers = [
14
+ "Programming Language :: Python :: 3",
15
+ "License :: OSI Approved :: MIT License",
16
+ "Operating System :: OS Independent",
17
+ "Environment :: Console",
18
+ ]
19
+ dependencies = [
20
+ "colorama>=0.4.6",
21
+ ]
22
+
23
+ [project.scripts]
24
+ stackforge = "stackforge.scaffold:main"
25
+
26
+ [tool.setuptools.packages.find]
27
27
  where = ["src"]
@@ -1,4 +1,4 @@
1
- [egg_info]
2
- tag_build =
3
- tag_date = 0
4
-
1
+ [egg_info]
2
+ tag_build =
3
+ tag_date = 0
4
+
@@ -1,8 +1,8 @@
1
- from .scaffolder import scaffold_folders
2
- from .csproj_generator import generate_csproj
3
- from .program_generator import generate_configure_services, generate_program_cs
4
- from .docker_generator import generate_dockerfile, generate_docker_compose
5
- from .config_generator import generate_env, generate_appsettings, generate_appsettings_development
6
- from .git_generator import generate_gitignore, generate_github_workflow, git_init
7
- from .api_generator import generate_api_structure
1
+ from .scaffolder import scaffold_folders
2
+ from .csproj_generator import generate_csproj
3
+ from .program_generator import generate_configure_services, generate_program_cs
4
+ from .docker_generator import generate_dockerfile, generate_docker_compose
5
+ from .config_generator import generate_env, generate_appsettings, generate_appsettings_development
6
+ from .git_generator import generate_gitignore, generate_github_workflow, git_init
7
+ from .api_generator import generate_api_structure
8
8
  from .layers_generator import generate_domain_layer, generate_application_layer, generate_infrastructure_layer, generate_persistence_layer