make it possible to stand up the blog locally

Question

make it possible to stand up the blog locally

Opened this issue 11 years ago · 14 comments

Add the pelican files to the repo so that design and technical contributors can work on the blog. by which I mean, the pelicanconf.py, publishconf.py, fab or make file, requirements.txt and anything else required to be able to stand up the blog locally so that we can test our changes.

make it possible to stand up the blog locally using the same method that is used in production
readify the process

Answer 1 · 2013-10-02T21:47:48.000Z

I don't use those to create the blog, so feel free to add them. I did add a simple build script that I use.

Answer 2 · 2013-10-02T21:52:41.000Z

Thanks. I might add them later because the devserver mode is helpful.

Answer 3 · 2013-10-02T21:53:26.000Z

What do I need to do to run a local version beyond installing pelican and running build.py?

Answer 4 · 2013-10-02T22:06:12.000Z

I don't know the answer to this. Jeff needs to document it (see #3). I deploy my pelican blog in an entirely different way and can't help.

Answer 5 · 2013-10-02T22:22:07.000Z

pip install -r requirements.txt
python build.py

open output/index.html in a browser.

I think there's a relative url setting that can be used to make sure css/js
show up nicely. I'll have to check on that later.

Jeff.

On Wed, Oct 2, 2013 at 6:06 PM, codersquid notifications@github.com wrote:

I don't know the answer to this. Jeff needs to document it (see #3 #3).
I deploy my pelican blog in an entirely different way and can't help.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/12#issuecomment-25581217
.

Answer 6 · 2013-10-03T02:18:22.000Z

Thanks. I think I'm almost there, but output/index.html is not populated by posts.

Answer 7 · 2013-10-03T02:42:52.000Z

Okay, got help from someone else to get up and running. Let's README-ify all this soon.

Answer 8 · 2013-10-11T14:21:53.000Z

Before I would consider this done, I agree that a readme should exist, and I also would like for contributors to be able to have a development environment that is as close to production as possible.

When people want to enhance or fix the site, they need to be able to test their changes in an environment that mimics production as closely as possible.

Answer 9 · 2013-11-22T18:44:28.000Z

Hey Jeff, can you look into the relative URL setting to display css/js? That's all we need to close this issue.

Answer 10 · 2013-11-25T18:29:14.000Z

Does changing site_url not solve the problem? Some templates don't handle relative URLs nicely. If that's the issue, then let's fire off another issue to change the template to handle them.

Answer 11 · 2013-11-25T18:40:11.000Z

Themes are working for me, but not images, and additionally it's difficult to navigate around the local site without accidentally going to the live site, because generated links are to osc.centerforopenscience.org.

Changing siteurl seems to break the theme without fixing any of the other two problems, although possibly I'm changing it to the wrong thing. What would you change it to?

Answer 12 · 2013-11-25T18:45:16.000Z

I think the theme requires changes then. I use a server that my IDE (pycharm) puts the site behind.

Answer 13 · 2013-11-25T18:50:01.000Z

Okay, I'm going to re-open this and look into changing the theme later.

Answer 14 · 2013-11-26T14:40:34.000Z

You could also open an issue on the template's repo; that would be where the contribution should go, and then we can merge it with our own changes to the template.