121–130 of 214 posts
It sounds great, but the permissions it needs is too much for me: > Repositories > Public and private > This application will be able to read and write all public and private repository data. Would it be possible to use deploy keys for specific repositories instead?
Hi HN. primo is an IDECMSCLSSG (short for IDE, CMS, Component Library, Static Site Generator) I’ve been working on for a few months. The idea came from wanting to host a Notion page at a domain name and not being able to. Once I made the initial version - a basic text editor - the rest of the features just came naturally (except for the SSG, which came from not wanting to deal with hosting). I’d written off freelance…
Free, but why do I need to login with GitHub to even try it?
Earlier quoted context omitted.
Thanks! Couldn't believe my luck on that one
Does Google treat .af (Afghanistan) as an international domain though? Not sure if they take the TLD into account much anymore when determining the regional focus of a page, I know some TLDs like .io and .ai are treated as non-regional, not sure about .af though. Problably not a large problem though, just haven't seen many .af product sites so far (really great, short domain name otherwise).
Why give this away? You could have a good business. You’re leaving money on the table.
I've told the story before, but we did a CMS very similar to this back in 1999/2000, and was able to charge 5-6 figures to Fortune 500 companies for a license. But that market crashed. CMS is just a specific flavor of CRUD apps, and most web devs can make one, so they just don't have the same price point as they used to.
That doesn't invalidate the work put into this CMS. I like what I can see of it. It looks like a good piece of work. But most CMS successes these days do give away the core tool for free, then make money on plugins, hosting, and services.
It sounds great, but the permissions it needs is too much for me: > Repositories > Public and private > This application will be able to read and write all public and private repository data. Would it be possible to use deploy keys for specific repositories instead?
Definitely. I thought I'd made it so you only need to give full permission on build, but either way individual repo access is ideal; I'll work on that next. Thanks.
It sounds great, but the permissions it needs is too much for me: > Repositories > Public and private > This application will be able to read and write all public and private repository data. Would it be possible to use deploy keys for specific repositories instead?
Private repos have to remain private. I don't own that code, I can't give it away. I was really excited to try this, too. Please fix this, I really want to give Primo a shot. :)
Earlier quoted context omitted.
.af (as fuck), pronounced "ah-foo" is cool af sounding tld. [0] https://www.urbandictionary.com/define.php?term=af
Where does the "ah-foo" pronunciation come from? I've never heard this before.
why does primo.af shows only part of content of https://primo.press/