{"id":21074848,"url":"https://github.com/nextlevelshit/navisaction","last_synced_at":"2026-03-27T03:49:54.856Z","repository":{"id":162186366,"uuid":"628972504","full_name":"nextlevelshit/navisaction","owner":"nextlevelshit","description":null,"archived":false,"fork":false,"pushed_at":"2023-05-12T00:02:39.000Z","size":483,"stargazers_count":0,"open_issues_count":2,"forks_count":0,"subscribers_count":3,"default_branch":"main","last_synced_at":"2025-01-20T22:41:48.117Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":"Vue","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/nextlevelshit.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2023-04-17T11:10:08.000Z","updated_at":"2023-05-08T11:21:20.000Z","dependencies_parsed_at":null,"dependency_job_id":"59972295-4226-4663-93a2-dbbef79311ff","html_url":"https://github.com/nextlevelshit/navisaction","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/nextlevelshit%2Fnavisaction","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/nextlevelshit%2Fnavisaction/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/nextlevelshit%2Fnavisaction/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/nextlevelshit%2Fnavisaction/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/nextlevelshit","download_url":"https://codeload.github.com/nextlevelshit/navisaction/tar.gz/refs/heads/main","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":243517475,"owners_count":20303637,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-11-19T19:18:20.875Z","updated_at":"2025-12-30T16:36:03.830Z","avatar_url":"https://github.com/nextlevelshit.png","language":"Vue","funding_links":[],"categories":[],"sub_categories":[],"readme":"# Navisaction PEERHOF 2023 ⛰️\n\nThis guide provides comprehensive instructions for setting up and maintaining a multi-container platform using Docker in\na production environment. It covers various tasks such as inspecting running containers, reverting to an earlier Git\ncommit and restarting containers, rebuilding and starting containers in the background, removing orphaned containers,\ninspecting volumes, and pulling logs into a temporary file.\n\n## Prerequisites\n\nBefore proceeding with the instructions, ensure that the following prerequisites are met:\n\n- Docker is installed on your machine.\n- Git is installed on your machine.\n- The project source code and configuration files are available locally.\n\n## Setup Instructions\n\nFollow the steps below to set up and run the multi-container platform:\n\n1. Clone the project repository:\n\n   ```shell\n   git clone \u003crepository-url\u003e\n   cd \u003cproject-directory\u003e\n   ```\n\n2. Create the `.env` file:\n\n    - In the project root directory, create a new file named `.env`.\n    - Add the required environment variables and their corresponding values to the `.env` file.\n    - Replace `\u003cvalue\u003e` with the appropriate values for your setup.\n    -\n\n3. Build the Docker images and start the containers:\n\n   ```shell\n   docker-compose up --build -d\n   ```\n\n   This command will build the Docker images for the services specified in the `docker-compose.yml` file and start the\n   containers in detached mode.\n\n\n4. Access the application:\n\n    - The application should now be accessible at the specified `APP_HOST` and `WEB_PORT` in your browser.\n\n## Maintenance Tasks\n\n### Inspecting Running Containers\n\nTo inspect the running Docker containers, use the following command:\n\n```shell\ndocker ps\n```\n\nThis command will display information about the running containers, including the container ID, image, status, ports,\nand names.\n\n### Reverting to an Earlier Git Commit and Restarting Containers\n\nIf you need to revert to an earlier Git commit and restart the containers, follow these steps:\n\n1. Find the commit hash for the desired earlier commit:\n\n   ```shell\n   git log\n   ```\n\n   This command will display a list of commits with their corresponding hashes.\n2. Note the commit hash for the desired earlier commit.\n\n\n2. Revert to the earlier commit:\n\n   ```shell\n   git checkout \u003ccommit-hash\u003e\n   ```\n\n   Replace `\u003ccommit-hash\u003e` with the commit hash you noted in the previous step.\n\n\n3. Rebuild and restart the containers:\n\n   ```shell\n   docker-compose up --build -d\n   ```\n\n   This command will rebuild the Docker images and restart the containers using the code from the earlier Git commit.\n\n### Rebuilding and Starting Detached Containers in the Background\n\nTo rebuild and start the containers in detached mode (background), use the following command:\n\n```shell\ndocker-compose up --build -d\n```\n\nThis command will rebuild the Docker images and start the containers in detached mode, allowing them to run in the\nbackground.\n\n### Removing Orphaned Containers\n\nTo remove orphaned containers, i.e., containers that are no longer in use, use the following command:\n\n```shell\ndocker-compose down --remove-orphans\n```\n\nThis command will stop and remove any containers that are not defined in the current `docker-compose.yml` file.\n\n### Inspecting Volumes\n\nTo inspect the contents of a volume, such as the `certs` volume in this project, use the following command:\n\n```shell\ndocker volume inspect \u003cvolume-name\u003e\n```\n\nReplace `\u003cvolume-name\u003e` with the name of the volume you want to inspect.\n\n### Inspecting Running Containers\n\nTo inspect the details of a running container, including its logs, network, and environment variables, use the following\ncommand:\n\n```shell\ndocker inspect \u003ccontainer-name\u003e\n```\n\nReplace `\u003ccontainer-name\u003e` with the name or container ID of the container you want to inspect.\n\nThis command will provide detailed information about the specified container, such as its configuration, network\nsettings, mounted volumes, and more. You can use this information for troubleshooting or gaining a deeper understanding\nof the container's runtime environment.\n\n### Pulling Logs into a Temporary File\n\nTo pull the logs from a running container into a temporary file, use the following command:\n\n```shell\ndocker logs \u003ccontainer-name\u003e \u003e logs.txt\n```\n\nReplace `\u003ccontainer-name\u003e` with the name or container ID\n\n# Contribution Guidelines\n\nThank you for your interest in contributing to this project! Contributions are highly appreciated. To ensure a smooth\ncollaboration, please follow the guidelines below.\n\n## Getting Started\n\n1. Fork the repository on GitHub.\n2. Clone your forked repository to your local machine.\n3. Create a new branch for your feature or bug fix.\n4. Make the necessary changes and additions.\n5. Test your changes thoroughly.\n6. Commit your changes with a descriptive commit message.\n7. Push your changes to your forked repository.\n8. Submit a pull request to the main repository.\n\n## Code Style\n\n- Follow the existing code style and conventions used in the project.\n- Maintain consistent formatting, indentation, and naming conventions.\n- Document your code and provide clear and concise comments where necessary.\n\n## Testing\n\n- Ensure that your changes do not introduce any breaking changes or regressions.\n- Write test cases to cover your changes whenever possible.\n- Run the existing test suite and make sure all tests pass successfully.\n\n## Documentation\n\n- Update the necessary documentation to reflect your changes.\n- Provide clear instructions and explanations for new features or modifications.\n\n## Contact\n\nIf you have any questions or need assistance, you can reach out to us:\n\n- Authors: Michael W. Czechowski\n- Email: github@dailysh.it\n\n## Greetings\n\nThank you for your interest and support in this project. We, GPT-4 and Michael W. Czechowski, have worked together to\ncreate this contribution guide. Your contributions make a significant impact, and your efforts are greatly appreciated.\nLet's build something awesome together!\n\n---\n\n*Note: The above contribution guidelines are meant to provide general guidance. Please refer to the specific guidelines\nand requirements mentioned in the repository's README or CONTRIBUTING.md file, if available.*\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fnextlevelshit%2Fnavisaction","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fnextlevelshit%2Fnavisaction","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fnextlevelshit%2Fnavisaction/lists"}