#Trying to export default static site
50 messages · Page 1 of 1 (latest)
i ran npm run build which runs next build which created the output without any noticeable errors in the console
is this normal for next or am i just doing this wrong?
what exactly are you doing?
after you run build, if you want it served you'll need to run next start
if it's a static site, should i just be able to open up index.html?
That's actually not how Browsers let you do things in a lot of cases
i intend to host this as a static site
with just natural html routing
Just because it's static, doesn't mean it doesn't need to be served
next export -h
still needs to be served
then what does the -h option do
you can't expect just any assets to work without a web server
it shows the help info for that command...
alright
thanks for your information
do you know of any SSG's that export sites that don't need to be served
you mean like nobody uses it?
i don't wanna host a web server on my site just yet because it's really expensive
i just want a static serverless site that says coming soon
web server on my site doesn't make sense, that's backwards
I think you probably misunderstand some basics
what do you actually want to deploy this to?
aws
... AWS serves you files
yes
that's a server
my personal site is aws
so you have a "server"
literally has "server" in its name
oh wow i had no idea
i remember setting something up in the past where a github repo was linked to something on aws
browsers expect files via HTTP...
where after i push my changes, aws would just copy it to the server
welp now you know
i just wanna do something like that