Create a General Standard that projects must follow #11

Open
opened 2024-12-10 15:48:57 -06:00 by ninjasurge · 3 comments
Owner

Create a standard for all projects to follow as a minimum, no matter the tech stack.

Create a standard for all projects to follow as a minimum, no matter the tech stack.
ninjasurge added the DiscussionFeature labels 2024-12-10 15:48:57 -06:00
Author
Owner

Every project needs to have a container compose file at the root through which the project is run.

Every project needs to have a container compose file at the root through which the project is run.
Author
Owner

Every project needs to have a container compose file at the root through which the project is run.

There needs to be editor plugins that will handle the running and integration of the compose file.

eg. Neovim will need a plugin that will find the compose file and make sure that it is running and run the compile or running commands inside the correct container...

> Every project needs to have a container compose file at the root through which the project is run. There needs to be editor plugins that will handle the running and integration of the compose file. eg. Neovim will need a plugin that will find the compose file and make sure that it is running and run the compile or running commands inside the correct container...
Author
Owner

There also needs to be a general config file that handles all the project specifics.

There also needs to be a general config file that handles all the project specifics.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: professional-projects/ninjasurge-application-requirements#11