No instructions for self-hosting

[akaihola]

We need the functionality of rawgithack, but hosted on our private network and pointed to our private repositories.

I tried to make this happen by attempting to run rawgithack locally, changing the URLs and fixing issues one by one. But eventually I hit a wall and faced problems which went above my understanding.

It would be fantastic to have instructions for modifying rawgithack for running our own copy.

[proudparrot2]

Not really sure if its meant to be replicated and self hosted, it just says that this repo is the source code behind it

[phanirithvij]

I made a fork and deployed locally.
It needs to be deployed on cloudflare for it to work as per design.

Here are the changes made https://github.com/phanirithvij/rawgithack
- url changes
- removal of patreon functionality (for purge-cache page)
- changed js endpoints for some hardcoded js files (required as domain is changing)

I have no plan to host a private version for myself just tinkered with it.

Commands I ran

rg githack%.com -l | xargs -n 1 sed -i 's/githack%.com/armyofrats%.in/g'
rg githack.com -l | xargs -n 1 sed -i 's/githack.com/armyofrats.in/g'
# manually replaced githack\.com in rawgithack.conf file
docker-compose --file .docker/docker-compose.yml down && docker-compose --file .docker/docker-compose.yml build && docker-compose --file .docker/docker-compose.yml up

[ramazansancar]

I made a fork and deployed locally. It needs to be deployed on cloudflare for it to work as per design.

Here are the changes made https://github.com/phanirithvij/rawgithack - url changes - removal of patreon functionality (for purge-cache page) - changed js endpoints for some hardcoded js files (required as domain is changing)

I have no plan to host a private version for myself just tinkered with it.

Commands I ran

rg githack%.com -l | xargs -n 1 sed -i 's/githack%.com/armyofrats%.in/g'
rg githack.com -l | xargs -n 1 sed -i 's/githack.com/armyofrats.in/g'
# manually replaced githack\.com in rawgithack.conf file
docker-compose --file .docker/docker-compose.yml down && docker-compose --file .docker/docker-compose.yml build && docker-compose --file .docker/docker-compose.yml up

I've started submitting the issue request. However, I'm having trouble with the documentation on how to get the project up and running smoothly, or how to launch it in development mode. After reviewing the code here, I figured I wouldn't have any problems. What are your thoughts on this? How would you go about integrating these changes throughout the project? @neoascetic

I believe a project running as a .env base will provide a seamless development environment. Additionally, if the cfg.patreon.token and cfg.patreon.campaign values for the Patreon domain are configured to work when submitted, depending on the .env domain, it would be much more effective for development mode.

[neoascetic]

For private hosting, I think the proper approach would be to throw out everything except the main nginx file, since it contains the core functionality. Cache invalidation isn't needed for private hosting I guess. UI is probably also unneeded.

[ramazansancar]

For private hosting, I think the proper approach would be to throw out everything except the main nginx file, since it contains the core functionality. Cache invalidation isn't needed for private hosting I guess. UI is probably also unneeded.

After development, it needs to be configured so that it can run smoothly in the production environment. @neoascetic
Therefore, there will be no need to remove existing features. Only features that work with a .env base will continue to work in the production environment. For the development environment, this will eliminate the need for developers to enter a .env in Patreon or Cloudflare.

[neoascetic]

I mean, the current implementation is all vendor-locked with cloudflare. The essence of the service is proxy. Someone would like to use other CDN provider etc. Furthermore, there are some settings I have in CF that basically are not in the repo. That's my point.

[ramazansancar]

I mean, the current implementation is all vendor-locked with cloudflare. The essence of the service is proxy. Someone would like to use other CDN provider etc. Furthermore, there are some settings I have in CF that basically are not in the repo. That's my point.

@neoascetic At the very least, seeing that the connections work smoothly locally will be sufficient for our development process. Being able to launch them with Docker provides a development environment without requiring special installations on every device.

In short, we can think of the address http://localhost:9000 as pointing to https://raw.githack.com/.

For example, in the live environment:
https://raw.githack.com/neoascetic/rawgithack/master/README.md

For the development environment:
http://localhost:9000/neoascetic/rawgithack/master/README.md

This will be quite sufficient for us.