GitHub action --> Publishment workflow

The project is split in two repositories:
https://github.com/publish-site/action
https://github.com/publish-site/backend

This project uses AI

On commit dcae7a9c43713f80700f701c9b5057993625135e of backend the LLM ChatGPT between line 78 and 83 AI was used because I didn’t know how returning properly worked, and had 1 problem with borrow checking.

Generally, if AI was used in this project, no agents was used, no code were pasted and I let the LLM understand the compiler error.
I use DuckDuckGo as a search engine, it has “Search assist” which basically summarizes information from other pages. I may have used that feature while searching for protocols or specific rust functions/macros.

Repository

anderson worked on GitHub action --> Publishment workflow

about 1 hour ago

0h 56m logged

Woo! The docker container is finally published! I’ve created a workflow that builds and publishes to https://github.com/publish-site/backend/pkgs/container/backend.

anderson worked on GitHub action --> Publishment workflow

about 2 hours ago

0h 17m logged

Hello! For the last few hours I’ve worked on getting colors into my program, YAY! Of course it checks if it is interactive, so the potential docker logs doesn’t risk getting cluttered with ANSI. I also removed some annoying debugging stuff, so that’s good to have out of the way. I made the program print the user agent for logging purposes, I may include more stuff like content length and such. I also started creating a wiki for both the backend and action! This will make it easier for the user to spin up their server and workflow.

NOTE: I don’t know why, but no time got logged with my neovim. Switching to Code OSS temporarily (?)

anderson worked on GitHub action --> Publishment workflow

about 18 hours ago

3h 15m logged

Phew! This was a long one. I finally implemented the upload logic for the backend server, meaning that I can finally upload the actual files! There is a few rough edges on the actions workflow, and I still have a bunch of debugging lines on the backend, and it’s still not writing anything. Either way I’m getting closer to done. I’m gonna focus on the completion, so first the upload part, then the authentication part. Finally after that I’ll clean up. Wish me luck!

Comments

anderson about 18 hours ago

Also, the server never actually completes the request yet (:

anderson worked on GitHub action --> Publishment workflow

2 days ago

1h 59m logged

I continued working on the backend side of this project, and made a docker image server to be deployed on the server. I implemented HTTPS by reverse-proxying through NGINX. The certs in the docker-compose file are intentionally left in the commit so you guys can check it out easier. Next steps are to create the actual frontend to be published to, and to initiate mTLS through nginx. Should be easy enough.

anderson worked on GitHub action --> Publishment workflow

2 days ago

1h 23m logged

I worked on the server-side part and has come up with a multithreaded HTTP server written in rust, see https://github.com/publish-site/backend. The next step is to implement HTTPS. I’m not sure if I wanna use this implementation due to potential security issues by user error (?) but I’ll try.

anderson worked on GitHub action --> Publishment workflow

3 days ago

0h 45m logged

Today I worked on the base actions workflow. The workflow is executing a script so far. Haven’t worked any on the “backend”. I also created a example workflow implementation.

0 Followers

Comments