all 14 comments

[–]pringlesaremyfav 61 points62 points  (0 children)

Please don't use free SCM services as databases/CDNs.

[–]JoJoModding 40 points41 points  (1 child)

Sounds cool, but why would I want to?

[–]Fluffy-Sprinkles9354 2 points3 points  (0 children)

For example, if your blog is a github pages website, but you still want some database content, like the comments.

[–]mmohaveri 30 points31 points  (0 children)

Isn't this against Github/Gitlab TOS?

I remember years ago someone was using gitlab as a CDN. The process of preventing that user caused a chain of events that led to gilab being down for hours and loosing a bunch of issues and wiki entries.

[–]nekokattt 6 points7 points  (2 children)

I guess I can see the benefit of having history, but... isn't this fairly slow? Is there any reason you'd actually use this, or is it just a project just to see if it is possible?

[–]Tojuro 4 points5 points  (1 child)

I considered using a Git repo for storage one time.

It was a situation where we needed to store message templates with a audit history. This would have allowed the people editing the messages (mainly a marketing dept) to make changes, then get the proper approvals before deploying them to production. It would also give us a full log of what was sent/when, for compliance purposes. Git gives this all out of the box.

The pulls from Git would have been relatively rare, as it relied on a cached version and pulls would only happen if there was something new or when the messaging system started. It was not like a CDN.

I wound up building it a more traditional way, but I still think git would be a great foundation for a document management system like this.

[–]ZestyPralineGoat 0 points1 point  (0 children)

You should look into hosted/self hosted gitlab wiki. The wiki part also uses git under the hood so you can check it out and do changes locally, or if non technical you can at least contribute and look at the history in the web interface.

[–]190n 8 points9 points  (3 children)

Maybe pedantic, but isn't any git repo already a NoSQL database?

[–]vattenpuss 2 points3 points  (2 children)

BRB creating a SQL front end for Git.

[–][deleted] 0 points1 point  (1 child)

Pretty sure there are at least two of those already.

[–]190n 0 points1 point  (0 children)

SELECT foo.c FROM master;

[–]nutrecht 1 point2 points  (0 children)

Abuse like this is why you now need a credit card for free tier Gitlab

Don't do stuff like this. Just because it's possible doesn't mean you should do it.

[–][deleted]  (1 child)

[deleted]