PrivateCoffee/structables
4
0
Fork 1
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Add Docker #6

Merged
kumi merged 2 commits from vlnst/structables:docker into main 2024-06-17 16:44:33 +00:00
Conversation 1 Commits 2 Files changed 6 +64 -5
vlnst commented 2024-06-17 15:59:45 +00:00
Contributor
Copy link

Changes:

  • Added a new instance: structables.bloat.cat
  • Implemented Docker support
  • Updated .gitignore to exclude user-specific Docker files

It would be beneficial to include documentation about Docker usage in the README.md file.

It would look something like this:

Copy .env.example to .env and adjust the settings.
Adjust settings in the docker-compose.yml file, such as modifying limits or changing the port configuration.

Also I'm not sure if including the https:// in README.md is necessary therefore you can probably get rid of it

127.0.0.1 is used in docker-compose-example.yml for a usage behind a reverse-proxy.

I can assist in setting up an automated workflow to build and publish Docker images in your registry. While I encountered issues with Forgejo Actions and switched to Woodpecker, I can still attempt to configure Forgejo Actions if needed. The two platforms should have similar functionalities. If you require assistance with setting up actions, feel free to let me know.

Changes: - Added a new instance: [structables.bloat.cat](https://structables.bloat.cat/) - Implemented Docker support - Updated .gitignore to exclude user-specific Docker files It would be beneficial to include documentation about Docker usage in the README.md file. It would look something like this: ``` Copy .env.example to .env and adjust the settings. Adjust settings in the docker-compose.yml file, such as modifying limits or changing the port configuration. ``` Also I'm not sure if including the `https://` in README.md is necessary therefore you can probably get rid of it 127.0.0.1 is used in `docker-compose-example.yml` for a usage behind a reverse-proxy. I can assist in setting up an automated workflow to build and publish Docker images in your registry. While I encountered issues with Forgejo Actions and switched to Woodpecker, I can still attempt to configure Forgejo Actions if needed. The two platforms should have similar functionalities. If you require assistance with setting up actions, feel free to let me know.
vlnst added 2 commits 2024-06-17 15:59:46 +00:00
kumi merged commit 0f91a929d2 into main 2024-06-17 16:44:33 +00:00
kumi deleted branch docker 2024-06-17 16:44:33 +00:00
kumi commented 2024-06-17 16:44:49 +00:00
Owner
Copy link

Hi! Welcome, and thank you very much for your contribution! I just tested it and it works beautifully.

I'll look into a README update to include some info on Docker deployments and maybe a Docker build workflow tomorrow, probably. Of course, pull requests for those two are also always welcome.

And thanks for running an instance, too!

Hi! Welcome, and thank you very much for your contribution! I just tested it and it works beautifully. I'll look into a README update to include some info on Docker deployments and maybe a Docker build workflow tomorrow, probably. Of course, pull requests for those two are also always welcome. And thanks for running an instance, too!
❤️ 1
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: PrivateCoffee/structables#6
No description provided.
Delete branch "vlnst/structables:docker"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?