Skip to content

Add installation info from metafacture/metafacture-documentation/pull/56 #22

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.

Sign up for GitHub

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Add installation info from metafacture/metafacture-documentation/pull/56 #22

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 23 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,8 @@ Since [Metafacture Fix](https://github.com/metafacture/metafacture-fix) is intro
It should help you to get accustomed with Metafacture Core and Metafacture Fix.
Have fun.

The content pages can be found [in `/docs/`](/docs/)

Lesson plan:

[01 Introducing metafacture](./docs/01_Introducing_Metafacture.md)
Expand All @@ -37,3 +39,24 @@ Lesson plan:

[11 Mapping Marc to Dublin Core](./docs/11_MARC_to_Dublin_Core.html)

## Testing

### Installation
If you are on debian derivates go install build-essentials:
```
apt install build-essential
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this work for anybody without sudo? At least it doesn't for me.

```
Then you can use the Ruby Dependency Management to build all you need:
```
bundle install
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After running sudo apt install build-essential and then bundle install, I get:

$ bundle install
Command 'bundle' not found, but can be installed with:
sudo apt install ruby-bundler

Is it only me or should installatioj of ruby-bundler also be added to the documentation?

However, after installing ruby-bundler, bundle install will start but throw errors for me. So, up until now I did not manage to start jekyll...

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the feedback, since it is the description from @dr0i which he introduced in metafacture-documentation, he probably can help

Copy link
Member

@dr0i dr0i May 22, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@acka47 could you try this (as root or sudoing and beeing in this repo's directory):

sudo apt remove ruby-bundler; sudo apt purge jekyll; sudo apt update; sudo apt install build-essential; bundle install; bundle exec jekyll serve

Ignore Warnings , the server should start at http://127.0.0.1:4000. If it does not , I am clueless.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@acka47 could you try this (as root or sudoing and beeing in this repo's directory):

sudo apt remove ruby-bundler; sudo apt purge jekyll; sudo apt update; sudo apt install build-essential; bundle install; bundle exec jekyll serve

Did so, bundle install works now but I get the same error I had before (after installing ruby-bundler, bundle install):

Gem::FilePermissionError: You don't have write permissions for the /var/lib/gems/3.1.0 directory

I did export GEM_HOME=$HOME/.gem/ruby/3.1.0/ as written in https://github.com/orgs/rubygems/discussions/6760#discussioncomment-6514401 and get another error:

Gem::Ext::BuildError: ERROR: Failed to build gem native extension.

This is getting on my nerves. If it works for others, you might already merge this PR.

```
Start jekyll like this:
```
bundle exec jekyll serve
```
If you experience troubles, make sure to not have jekyll installed via you
package manager. On debian derivates do:
```
apt purge jekyll
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here: Does this work for anybody without sudo? At least it doesn't for me.

```