starshipwinepineapple

joined 4 months ago
[–] starshipwinepineapple 13 points 3 months ago

Never. For the most part i haven't had a question that hasn't already asked or that couldn't be answered from reading the docs or some other source. For the cases i get stuck i ask the question to a more focused group

[–] starshipwinepineapple 7 points 3 months ago

My company ones are always super obvious. One of the best ones though was on valentines day spoofing a valentines ecard from a coworker in your organization

[–] starshipwinepineapple 3 points 3 months ago

And if you want a private repo, you can also use gitlab and point to custom domain with gitlab pages or cloudflare pages.

[–] starshipwinepineapple 17 points 3 months ago* (last edited 3 months ago) (1 children)

Yes, oracle will reclaim your server if it falls under certain thresholds for the resources you've signed up for. So it might be better to request less resources then you need but this will somewhat complicate things if you want more resources in the future since iirc you can't simply resize.

One way to get around all of this though is convert to pay as you go (PAYG). PAYG gets the same always free allocations and you only pay for use above that, and oracle won't reclaim PAYG (at least not my server for ~4 years). Just set up a budget of a $1 and then alerts to email you if you reach 1% of your budget. If you somehow go over your free resources it'll tell you.

Lastly in some cases oracle just straight up loses your data or disables your account. As always practice 3-2-1 backups (don't rely on the free rotating backups on their servers as your only backup).

It's some hoops to jump through but i was paying $5/ month for a digital ocean droplet and the oracle server has been running for 4 years now, and i also have scaled up one project and started a few others that wouldn't have all fit on my droplet. Other than the threat of reclaiming my resources before i switched to PAYG I've been pretty happy with it.

[–] starshipwinepineapple 1 points 3 months ago

It would be a good idea to at least buy one or several domain .TLDs for open source projects even if you currently aren't planning to make use of them. If nothing else getting a domain prevents someone else from registering it, and you could start using them to make legitimate results higher in search results. This is easiest when you are first starting a project and can check availability before settling on a name.

The problem is that there are hundreds of TLDs so you're not going to be able to register them all. Simplex mentioned they reported the domain. If you do an ICANN lookup you can find an abuse email for the domain, which would be an email for the registrar. You can report to that email and it is likely they will remove the site. You can also go directly to the TLD and report abuse to them as well.

Beyond that search for your project every once and a while and see what comes up or what doesn't come up.

[–] starshipwinepineapple 2 points 3 months ago* (last edited 3 months ago)

The first part of the article talks about how to use git notes and has an example commit, followed by adding the note, and then viewing the note. This is all native git.

The "problem" is that we have centralized discussions in github/gitlab comments and if we want to retain that data then we need to convert the comments into gitnotes. The CLI part is that specific discussion on how Symfony uses git notes to store github comments. It references an internal CLI but then goes through an example of how to use github api to fetch the comments, create git notes, then push those git notes to github. So while the symfony CLI is internal, it looks like we're given an example of how to do this for github.

[–] starshipwinepineapple 22 points 4 months ago* (last edited 4 months ago) (6 children)

Ive been meaning to move to codeberg, self hosted forgejo, or sourcehut so this will only accelerate that if things get worse.

[–] starshipwinepineapple 4 points 4 months ago

Thanks! I'll add that to my list to check out

[–] starshipwinepineapple 4 points 4 months ago* (last edited 4 months ago)

If you only ever keep your repository private AND it is not a fork of a public repo, then you are fine. Full stop.

If you ever fork the repo and make a "INTERNAL" private fork but move the main project public then anything you commit to the private fork will be discoverable through the public project.

Basically you should assume if you make a repo public then the repo and all of its forks will be public-- even if the forks are "private" the commit data can be found through the main repo.

[–] starshipwinepineapple 9 points 4 months ago (2 children)

Well to speak of the obvious- open source. I've heard good things about obsidian but i am not trusting a closed source app with my notes/ mind-maps

This project looks pretty promising, and is open source.

[–] starshipwinepineapple 7 points 4 months ago (1 children)

Pull request aka merge request. Part of the approval process to add/ update code in a repository

view more: ‹ prev next ›