Added Dockerfile for making the image, .gitea for .gitea/workflows with action runners, and bin directory with purely docker-image-making scripts
Message me if you wanna set this up so whenever you push to branch: docker_upload it will automatically update the server's webpage instead of waiting for me to update it myself
Or just ignore this, I'll prob just set up a system that'll git pull and update the files periodically, later, if I'm bored, really bored
Also I fixed your requirements.txt because I'm awesome and have a big cock
### Added `Dockerfile` for making the image, `.gitea` for `.gitea/workflows` with action runners, and `bin` directory with purely docker-image-making scripts
#### Message me if you wanna set this up so whenever you push to branch: `docker_upload` it will automatically update the server's webpage instead of waiting for me to update it myself
#### Or just ignore this, I'll prob just set up a system that'll git pull and update the files periodically, later, if I'm bored, really bored
#### <u>Also I fixed your **requirements.txt**</u> because I'm awesome and have a big cock
There might be a way to do that, the issue with that is that gitea looks at the files (Dockerfile and ./bin files) to execute the gitea runner thing. I wouldn't know how to do that though, I tried hiding it all in the .gitea folder so that it would be hidden but it didn't quite work since the runner seemed to not be able to see them
There might be a way to do that, the issue with that is that gitea looks at the files (Dockerfile and ./bin files) to execute the gitea runner thing. I wouldn't know how to do that though, I tried hiding it all in the .gitea folder so that it would be hidden but it didn't quite work since the runner seemed to not be able to see them
This pull request has changes conflicting with the target branch.
requirements.txt
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Added
Dockerfilefor making the image,.giteafor.gitea/workflowswith action runners, andbindirectory with purely docker-image-making scriptsMessage me if you wanna set this up so whenever you push to branch:
docker_uploadit will automatically update the server's webpage instead of waiting for me to update it myselfOr just ignore this, I'll prob just set up a system that'll git pull and update the files periodically, later, if I'm bored, really bored
Also I fixed your requirements.txt because I'm awesome and have a big cock
It seems weird having files in the repo that are used for managing the repo itself. Could you put the scripts in /bin somewhere else?
There might be a way to do that, the issue with that is that gitea looks at the files (Dockerfile and ./bin files) to execute the gitea runner thing. I wouldn't know how to do that though, I tried hiding it all in the .gitea folder so that it would be hidden but it didn't quite work since the runner seemed to not be able to see them
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.