-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Set config.json to serve Drummer blog and render/serve local html/opml files? #28
Comments
The best way to approach this imho, is to forget for a moment what you're telling PP to do, but rather, what you want to be done. And write it down, carefully, using common web terminology, so that you're sure anyone who understands how the web works will understand what you want to do. That part is your responsibility. No one can read your mind. And no one can solve problems like that without a clear understanding of what the goal is. Unscatter this, and you know what -- I don't think you're going to need any help. |
Using the http://theviewfromafar.com/ domain hosted on my Digital Ocean pagePark, I want to serve these pages in your cloud-based Drummer: Then I want to serve every other page of .md, .opml, and .html from /domains/theviewfromafar.com folders and/or subfolders. I get stuck on using: Thank you! |
Another specification of the issue: A config.json of: |
Using pagePark on Digital Ocean droplet. [It works!] In pagePark, tried config.json of :
{
"urlSiteContents": "http://oldschool.scripting.com/sbwTweet"
}
In browser, the blog rendered, but then browser would show locally stored ".opml" files unrendered.
Then tried:
{
"defaultExtension": "opml",
"urlSiteContents": {
"/": { "http://oldschool.scripting.com/sbwTweet"
}
}
Browser showed local ".opml" file rendered, but browser showed blog as a 404.
Goal is to get Drummers’ Blog, Links, and About to show in browser and then serve other ".html" and ."opml" files to serve/render from pagePark files in the domains folder.
Didn’t find in the docs, comments where this is addressed. Thank you for help and or pointers.
The text was updated successfully, but these errors were encountered: