0x20f/carbon

Build tool for custom configuration of multiple smaller services, and wrapper commands for docker containers to make your life easier.

Personal portfolio summary at 0x20f.com

carbon's Issues

Logs for the stop command

Everything should match all other commands

Parameter for adding dotenv file

• Provide a way to set env file by number
• Move the current foothold file to ~/.local/carbon-foothold.toml
• Create a new file in /tmp/carbon-emissions.toml and store the running services in there. This'll be the session database
• Provide a way to show indexed env files in a numbered list
• Provide a way to add new env file paths, if parameter isn't provided, check current directory for it and add it to the config as active
• Whenever commands are run, use the active env file as a starting point, unless override parameter is provided
• If parameterr with new env file is provided, add it to the list and set as active

Rebuild command for service

Take the container down and rebuild it with updated data or whatever it may need.

Documentation for everything

Docs for all undocumented code

Allow for descriptor files for development

Besides the carbon.yml file in each service, there can be a carbon-isotope.yml file that contains the descriptions of that exact same service but for development.

Maybe different port mappings, volumes, images, whatever.

• Carbon will then have to read the isotope file it it's being told.
• Maybe if all service names that start with c- should be run from the isotope file. Like c-artemis for example.

Store command

• New command to add directories for carbon files
• Carbon should then look in all the paths in the store
• Proper logs for the store command

Stop command for services

Do the opposite of start.

• this will require keeping track of what services are part of what compose files
• which in turn will mean keeping track of each compose file

README Update

It's good to have a file describing everything this package can do as well as what it's actually meant for. Whether it goes public or not, it's nice to have.

Output created compose file

A subcommand to output the docker-compose file that is built out of all the specified services to a specific path. This is useful if that compose file needs to later be given to a docker swarm deploy or something similar.

Something like: co2 save ./

• Subcommand for telling the application that we just want the output
• Subcommand value should be the path to output to
• Fully expand path so it gets saved where it should
• Don't add anything extra to the generated compose file (like container names and so on), just straight up copy pasting...
• Save into the provided path, whether its a file or not, the user's job to be specific.

Show networks

Pull in serde, for starters since the docker CLI has a command that returns information about a network as json.

Use that to dynamically build a nice summary of all networks.

Speed up network list command

• Run the network inspect command with all containers at once instead of separate.
• Allow serde to parse into a Vec of Network objects so the trimming doesn't have to happen.