Hi, great questions!

1. Git pages allow hosting dynamic sites if the code works in the browser - most nostr apps are like that. Our engine can work on the server and in the browser, it connects directly to relays and converts events to html pages. Our hosting runs the code both on the server (to pre-render for search engines) and in the browser after the first page is loaded (to save our resources and to enable offline work). The self-hosted option we're offering is currently limited to browser-side rendering - so it can be hosted on Git pages, but can't be crawled by search engines properly. Server side engine coming later (won't work with Git pages as it will require nodejs).

2. Yes you can attach a custom (sub)domain with our hosting, and you definitely can add it if self-hosting.

3. Our alternative to your /blog/ collection would just be /posts/ (for long-form articles), and with static pages coming soon you'd be able to override the homepage and make other static pages like About me.

I suggest you just try npub.pro, and try importing a couple posts from your Ghost site and try playing with it. It should take 10 minutes to do all that and have something usable. You can always attach custom domain or self-host later, there's no "migration" - it's nostr, all the data is out there.

Reply to this note

Please Login to reply.

Discussion

The last point is key, thanks!

Based on that, I will try it out! I guess It didn't sink it yet the "no migration" part, we are just so used to it, so didn't want to start something, to later just re do it all if migrate and self host.

"You can always attach custom domain or self-host later, there's no "migration" - it's nostr, all the data is out there."

Exactly! That's the beauty of nostr! And thanks for the zap!

You are welcome. thank you for the open info.

nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq3uamnwvaz7tmwdaehgu3dwp6kytnhv4kxcmmjv3jhytnwv46z7qpqxdtducdnjerex88gkg2qk2atsdlqsyxqaag4h05jmcpyspqt30wsqcfvpv GM!, I create a npub pro site yesterday, really fast, sweet. I like the tags filter for the homepage, navigation and other custom options, AND that it has code injection section, really cool.

After creating the site, I gave it a try to the self hosted version, to complicate my life more I hosted it on Netifly as for test I figure it would be easier, just drag and drop the zip file and connect my subdomain. that site is now here https://nostr.javierfeliu.com/ .

I change the "website address" on the npub admin panel. to this new address. The npub site is https://javier.npub.pro/

First issue is that I obviously have two site, how do I keep the self host version if I desire to, without having two versions? I guess I could delete, but that will no longer give me the option to download the zip file every time I make an update to settings, correct?

Second, I try to connect my domain in npub pro, but then I realize it will conflict with my set up in netifly, as essentially will direct both to the same subdomain. AND that is for the paid pro version you offer (wish I very well take at some point). I am just playing with it right now. If, selfhosted, I just change the web address, but not touch domain right? (as seen in the instructions) I just add the records npub ask if I am planning to take your premium tier?

The version hosted in your server, its considerably faster to load.

On phone, i can zap both sites, no problem, on desktop just the npub version, not the self hosted(it stay loading..)

Thank you for any feedback if you have some!

Have a good day

nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq3uamnwvaz7tmwdaehgu3dwp6kytnhv4kxcmmjv3jhytnwv46z7qpqxdtducdnjerex88gkg2qk2atsdlqsyxqaag4h05jmcpyspqt30wsqcfvpv GM! any feedback on this will be much appreciated and zaps will be sent for sure 😅 . To try to finish a set up. I try to read on the blog and other docs, but do not find these answers.

Hi, sorry for long reply, was away for a couple days.

You don't need to re-upload the zip file after each settings update - settings are saved on nostr and the code inside zip file will take new settings from nostr. The only reason to reupload the zip file would be some big updates to our code (minor updates are auto-propagated now).

For now we're just rendering all sites on our servers - there are probably less then a dozen of self-hosted ones so we didn't bother to come up with special handling for them. The only real issue with having two sites is duplicate content that might confuse Google - but you won't be getting much search traffic anyways for starters, so that's not a big priority for now.

If you attach your subdomain to npub.pro then it will no longer point to netlify (you'll need to remove netlify's dns records), so there can't be much conflict there. I'm not sure I understand the question about the paid plan and DNS settings, please let me know more.

Re. zaps - I just zapped on your self-hosted site, there shouldn't be any difference, please try reloading the page or clear cache etc.

The self-hosted version is client-side rendered, so first page load is slow, but then both self-hosted and us-hosted versions work the same - rendering happens in the browser, so they should be equally fast after the first load. Server-side rendered self-hosted version will be available later.

Thanks for a lot of feedback!

thanks!

1) the zaps are working fine, try it the next day and was working.

2) I was guessing that changes to the theme, navigation or code injection, will require and update to the self hosted code, is that not correct? I do understand that normal nostr profile settings will be made on any client and reflect there without need of re upload nothing.

3) Yes, that was worry ( not really big at all) the content duplication....but was mostly courios if I was missing something.

4) The question about Dns settings and the subdomain attachment is: As a self hosted user, can I point the npub site to my netifly, but I am understanding right now by your answer, that I can not.

When I mentioned the pay plan, is that when I start the configuration of my own domain from npub settings, I am lead to upload some records, cname and text, because the "your own domaim" is a setting for the pay plan, I was guessing this really has no use if I self host, so I do not need to add any npub records on my dns except to point to my npub site as I currently have it. hope that make sense.

Because you already said the npub version. Will be keep on being life, I am guessing there is no point in messing with that domain configuration from the settings panel, unless I am on the paid plan

**...please if those not make sense, ignore. once I am consistent in content I may delve deeper, I do not want to waste your time!**

Thanks!!

> 2) I was guessing that changes to the theme, navigation or code injection, will require and update to the self hosted code, is that not correct?

No, all changes you make in admin panel are saved on nostr as a special event kind and thus are fetched by self-hosted code, no need to update it. Well, technically site name or icon are printed in a manifest file which would need to be reuploaded so that these changes would be visible if people add site to homescreen (PWA), but I'd say it's a minor concern. It would only be absolutely necessary to reupload if we made significant changes to the site engine code.

> can I point the npub site to my netifly

No, you can't point subdomain.npub.pro to netlify.

> this really has no use if I self host, so I do not need to add any npub records on my dns

If you self-host, you don't need our dns settings. You can attach a custom domain on a site hosted by us for free while we're testing in public and don't have paid plans launched yet.

Thanks for asking, this helps us understand the sources of potential confusion!

this clarify all the doubts for sure!!! and I am clear now with the code being hosted but almost all settings (not just posts) being events on nostr. Again, it is a whole new way of thinking.

thank you!!