solomax commented on PR #1:
URL: https://github.com/apache/openjpa-site/pull/1#issuecomment-2222565685

   > Thanks @solomax Would you mind to share how you managed to build the 
website locally?
   
   DISCLAIMER: some of the steps were required to avoid pollution of my laptop 
with various Python file/folders
   
   - create empty folder all files will be stored (for ex. 
`~/work/site-pelican`)
   - `cd ~/work/site-pelican` 
   - set up `pyenv`
     - `git clone https://github.com/pyenv/pyenv.git .pyenv`
     -  `cd .pyenv && src/configure && make -C src`
     - create file `pyenv.sh` with following content:
   ```
   export PYENV_ROOT="${HOME}/work/site-pelican/.pyenv"
   command -v pyenv >/dev/null || export PATH="$PYENV_ROOT/bin:$PATH"
   eval "$(pyenv init -)"
   ```
     - run `source pyenv.sh`
     - install Python 3.8.10: `pyenv install 3.8.10`
     - `pyenv global 3.8.10`
   - download original 
`https://raw.githubusercontent.com/apache/infrastructure-pelican/master/bin/local-pelican-site.sh`
   - I did the following changes:
   ```
   --- local-pelican-site.sh.orig       2024-07-11 17:11:16.887533118 +0700
   +++ local-pelican-site.sh.new        2024-07-11 17:08:22.698213396 +0700
   @@ -8,10 +8,12 @@
    # will not work under basic Windows.
    
    # github prefix for cloning/updating repos
   -GH="https://github.com/apache";
   +GH="g...@github.com:apache"
    
    # site_build directory path. use a /tmp dir by default
   -SB="$HOME/pelican-local"
   +#SB="$HOME/pelican-local"
   +#SB="$HOME/work/_oss/site-pelican"
   +SB="$HOME/work/site-pelican"
    
    # infrastructure-pelican repo
    IP="infrastructure-pelican"
   @@ -74,7 +76,7 @@
    else
      echo "Cloning $IP"
      # Sometimes useful to add -b <branch> for buildsite testing
   -  git clone $GH/$IP 2>&1
   +  git clone $GH/$IP.git 2>&1
    fi
    
    IP="$SB/$IP"
   @@ -86,7 +88,7 @@
      # cd $REPO && git pull > /dev/null && cd ..
    else
      echo "Cloning $REPO"
   -  git clone $GH/$REPO 2>&1
   +  git clone $GH/$REPO.git 2>&1
    fi
    REPO="$SB/$REPO"
    # deploy our pipenv if we haven't already
   @@ -96,7 +98,7 @@
    if [ ! -f "Pipfile.lock" ];
    then
      echo "Setting up pipenv..."
   -  pipenv --three install -r $IP/requirements.txt > /dev/null 2>&1 || 'echo 
"pipenv install failed!" && exit -1'
   +  pipenv install $(< $IP/requirements.txt) || 'echo "pipenv install 
failed!" && exit -1'
    
    else
      echo "Pipfile.lock found, assuming pipenv exists."
   ```
   - run `bash local-pelican-site.sh openjpa-site`
   - got some errors from `pipenv install`
   - modify `infrastructure-pelican/requirements.txt` remove all comments 
starting with `# `
   - Build gfm
     - `cd cmark-gfm-0.28.3.gfm.12/build`
     -  `cmake --install-prefix $PWD/.. ..`
     - `make`
     - `make install`
   - `cd ../..`
   - cd `openjpa-site`
   - `git checkout 4.0-site-update`
   - `cd ..`
   -  run `bash local-pelican-site.sh openjpa-site`
   
   something like this :))
   
   Sorry for the mess
   
   I'm not really like Python :(


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@openjpa.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to