Skip to content
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

dockerify trac-hub #26

Open
bwl21 opened this issue Mar 10, 2019 · 4 comments
Open

dockerify trac-hub #26

bwl21 opened this issue Mar 10, 2019 · 4 comments

Comments

@bwl21
Copy link

bwl21 commented Mar 10, 2019

First of all I need to express that trac-hub is awesome. After spending some days with tracboat and other scripts this is the first stuff which ended in promising results at github (maybe because it is written ruby :-)

This morning I played with trac-hub. I used docker for that:

FROM ruby:2.5

# throw errors if Gemfile has been modified since Gemfile.lock
RUN bundle config --global frozen 1

WORKDIR /usr/src/app

COPY Gemfile Gemfile.lock ./
RUN bundle install

COPY . .

ENTRYPOINT cd /usr/src/myapp/trac-hub && bash

I start it with docker-compose

  mysql:
    image: mysql:5.7
    restart: unless-stopped
    environment:
      - MYSQL_ROOT_PASSWORD=password
    ports:
      - 3306:3306
    volumes:
      - mysql:/var/lib/mysql

 trac-hub:
    image: bwl21/trac-hub
    build: trac-hub

    restart: unless-stopped

    volumes:
      - .:/usr/src/myapp
      - /Users/beweiche/gitlab/data:/var/opt/gitlab
    links:
      - mysql
    depends_on:
      - mysql

Inovoke as

docker-compose run --rm trac-hub
bwl21 pushed a commit to bwl21/trac-hub that referenced this issue Mar 12, 2019
it is still such that you need to run trachub command from the docker file
@mavam
Copy link
Owner

mavam commented Mar 14, 2019

First of all I need to express that trac-hub is awesome

Great to hear that it works for you!

I have to admit that I find a Docker image a bit overkill for a simple Ruby script, but I'm happy to review/merge PR that contributes a Dockerfile.

@bwl21
Copy link
Author

bwl21 commented Mar 14, 2019

I have to admit that I find a Docker image a bit overkill for a simple Ruby script, but I'm happy to review/merge PR that contributes a Dockerfile.

not really, as I read the data from mysql, I also need an mysql server. I found it pretty easy to come going without installing a lot of stuff o my machine.

TBH I am not sure if pr makes sense, since I experience that the migration process is not generic enough. I have to adapt our methods and process to gitlab and then see how we can convert it.

I hacked lots of changes specific for my project. Of course I will publish the changes in a fork so interested people can grab code from there.

@mavam
Copy link
Owner

mavam commented Mar 14, 2019

Ah, I already forgot about the MySQL part. In that case, yes. I think having your Dockerfile, even if it's quite specific, would be of benefit to look at for others.

bwl21 pushed a commit to bwl21/trac-hub that referenced this issue Mar 22, 2019
There are too many changes to open a PR. nevertheless this also covers
mavam#30
mavam#28
mavam#27
mavam#26
ronaldtse added a commit to riboseinc/trac-hub that referenced this issue Jul 4, 2021
* bwl21-master:
  updated readme with hint to gitlab
  This is the wrap-up of my migration done based on tram-hub
  optimized ticket opening
  now handle attachments
  .gitignore .idea
  improve layout of transferred tickets - separate labels from badges
  export trac states to info
  improve logging and feedback to the user
  improve mapping of changes references
  improve mapping of assignee
  fixed milestone due dates
  replace full ticket urls by appropriate ticket links
  fix handling of revmap
  now handle milestones, some refinement of ticket layout
  see mavam#26 created a docker file to run trachub
  mavam#27 adapted markdownify to process header 1 correctly and not place ticket content in a quote
  see mavam#28 keep github and trac numbers in sync even if trac tickets id are not consecutive
  see mavam#30 implemented info  in ruby
@dwt
Copy link

dwt commented Oct 7, 2021

I would like to say that dockerizing the repo would also document all the required versions of used components. That is what I'm currently struggling with, so…

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants