Logs for #nikola for 2022-12-26

02:23:45 <LohanG> Hello! At last I was able to get hold of my backup of my old nikola blog, which I am now trying to resume publishing. I have now copied the source files to my new machine. This means I already have a directory at ~/nikola/. Inside it I have my blog. ~/nikola/blog/ . I have installed python3-pip. I am now looking at nikola installation steps for gnu/linux. It says python3 -m venv nikola
02:24:10 <LohanG> Will this step affect/erase or reinitiate  my source folder?
02:27:16 <LohanG> How should I import my old blog into my new machine's nikola setup? Should I first do a pip install nikola? Installation steps on the homepage is a little confusing to me. On one hand it tells me to install it with 'pip install nikola' and on the rignt column it provides a different step. python3 -m venv nikola
02:28:29 <LohanG> Oops, I am sorry I misread the instructions. I will give it another try. It's been a while since I last installed it.
02:30:08 <LohanG> I still have my first question : how should I start importing my blog into my new machine's setup?
03:11:03 <LohanG> Since nikola is sort of tied to a particular computer, it would be great if someone could write a guide on how to migrate it to a different machine. I am aware that some people use platforms like git. But for a non-programmer like myself it adds a very complex learning curve. I chose nikola because it is lightweight and static. And image galleries work great :)
08:42:55 <LohanG> Well, I went ahead and followed all the installation steps while having the blog directory inside nikola directory. All went well. Problem solved. Please ignore my question above. Happy holidays everyone o/
11:09:33 <ChrisWarrick> LohanG: Nikola is not tied to a particular computer. Python virtual environments are, but Nikola sites can be maintained on multiple computers.
11:10:47 <ChrisWarrick> LohanG: The nicest way to set things up involves either making the venv a separate folder somewhere else (eg. ~/virtualenvs/nikola vs ~/website), or making the venv a child of your Nikola source tree (~/website/.venv)
11:58:56 <LohanG> hi ChrisWarrick o/
11:59:49 <ChrisWarrick> hi :)
12:00:41 <LohanG> Yes, I should have had the sorce files with me, and the knowledge that copying it to the same location and installing nikola from 0 will do the job. My blog became dormant since 2021 because I didn't have access to the source files
12:01:21 <LohanG> In my case it was tied to the old computer I used
12:01:45 <LohanG> All is good now :)
12:02:04 <ChrisWarrick> great!
12:03:58 <LohanG> Does venv mean a virtual environment?
12:05:52 <LohanG> ah yes it is
12:09:29 <LohanG> By the looks of it I never had a directory named venv or virtualenvs associated with my blog. Should I be concerned about it? 
12:12:25 <ChrisWarrick> not necessarily
12:12:43 <LohanG> Ah okay...
12:12:47 <ChrisWarrick> venvs don’t have to be named venv, you can use any other style as long as it works
12:12:57 <ChrisWarrick> mixing your venv (bin, lib, etc) with nikola sources is something that would be concering
12:13:29 <LohanG> I am sure I did not make any changes to the way it came. I simply followed the install instructions on the website. 
12:13:56 <LohanG> I am able to generate the site now
19:17:50 <KwBot> [nikola] g1ra opened issue #3654: ERROR: Two different tasks can't have a common target.'output/images2/illus_001.thumbnail.jpg' https://github.com/getnikola/nikola/issues/3654
19:32:22 <KwBot> [nikola] g1ra closed issue #3654: ERROR: Two different tasks can't have a common target.'output/images2/illus_001.thumbnail.jpg' https://github.com/getnikola/nikola/issues/3654