jinda 0.7.7.4 → 1.0.0

data/test/dummy/config/puma.rb

@@ -1,43 +1,44 @@
+# This configuration file will be evaluated by Puma. The top-level methods that
+# are invoked here are part of Puma's configuration DSL. For more information
+# about methods provided by the DSL, see https://puma.io/puma/Puma/DSL.html.
+
 # Puma can serve each request in a thread from an internal thread pool.
 # The `threads` method setting takes two numbers: a minimum and maximum.
 # Any libraries that use thread pools should be configured to match
 # the maximum value specified for Puma. Default is set to 5 threads for minimum
 # and maximum; this matches the default thread size of Active Record.
-#
 max_threads_count = ENV.fetch("RAILS_MAX_THREADS") { 5 }
 min_threads_count = ENV.fetch("RAILS_MIN_THREADS") { max_threads_count }
 threads min_threads_count, max_threads_count
 
+rails_env = ENV.fetch("RAILS_ENV") { "development" }
+
+if rails_env == "production"
+  # If you are running more than 1 thread per process, the workers count
+  # should be equal to the number of processors (CPU cores) in production.
+  #
+  # It defaults to 1 because it's impossible to reliably detect how many
+  # CPU cores are available. Make sure to set the `WEB_CONCURRENCY` environment
+  # variable to match the number of processors.
+  worker_count = Integer(ENV.fetch("WEB_CONCURRENCY") { 1 })
+  if worker_count > 1
+    workers worker_count
+  else
+    preload_app!
+  end
+end
 # Specifies the `worker_timeout` threshold that Puma will use to wait before
 # terminating a worker in development environments.
-#
 worker_timeout 3600 if ENV.fetch("RAILS_ENV", "development") == "development"
 
 # Specifies the `port` that Puma will listen on to receive requests; default is 3000.
-#
 port ENV.fetch("PORT") { 3000 }
 
 # Specifies the `environment` that Puma will run in.
-#
-environment ENV.fetch("RAILS_ENV") { "development" }
+environment rails_env
 
 # Specifies the `pidfile` that Puma will use.
 pidfile ENV.fetch("PIDFILE") { "tmp/pids/server.pid" }
 
-# Specifies the number of `workers` to boot in clustered mode.
-# Workers are forked web server processes. If using threads and workers together
-# the concurrency of the application would be max `threads` * `workers`.
-# Workers do not work on JRuby or Windows (both of which do not support
-# processes).
-#
-# workers ENV.fetch("WEB_CONCURRENCY") { 2 }
-
-# Use the `preload_app!` method when specifying a `workers` number.
-# This directive tells Puma to first boot the application and load code
-# before forking the application. This takes advantage of Copy On Write
-# process behavior so workers use less memory.
-#
-# preload_app!
-
 # Allow puma to be restarted by `bin/rails restart` command.
 plugin :tmp_restart

data/test/dummy/config/routes.rb

@@ -1,7 +1,13 @@
 Rails.application.routes.draw do
   root :to => 'jinda#index'
+  get 'mindmap_editor/edit'
+  post 'mindmap_editor/save'
   # Define your application routes per the DSL in https://guides.rubyonrails.org/routing.html
 
+  # Reveal health status on /up that returns 200 if the app boots with no exceptions, otherwise 500.
+  # Can be used by load balancers and uptime monitors to verify that the app is live.
+  get "up" => "rails/health#show", as: :rails_health_check
+
   # Defines the root path route ("/")
-  # root "articles#index"
+  # root "posts#index"
 end

data/test/dummy/docker-compose-mongodb.yml

@@ -0,0 +1,13 @@
+services:
+  mongodb:
+    image: mongo:latest
+    container_name: jinda_mongodb
+    ports:
+      - "27017:27017"
+    volumes:
+      - mongodb_data:/data/db
+    environment:
+      - MONGO_INITDB_DATABASE=jinda_development
+
+volumes:
+  mongodb_data:

data/test/dummy/docker-compose-web.yml

@@ -0,0 +1,36 @@
+# docker-compose-web.yml - Full stack with web application and MongoDB
+# For development with local gem modifications:
+#   1. Add volume mounts for your local gem paths:
+#      volumes:
+#        - .:/myapp
+#        - ~/mygem/jinda:/path/to/local/jinda
+#        - ~/mygem/jinda_adminlte:/path/to/local/jinda_adminlte
+#   2. Update Gemfile to use path: '/path/to/local/jinda'
+
+services:
+  web:
+    build: .
+    env_file: .env
+    command: bash -c "rm -f tmp/pids/server.pid && bundle exec rails s -p 3000 -b '0.0.0.0'"
+    volumes:
+      - .:/myapp
+      # TODO: Add your local gem paths here for development
+      # - ~/mygem/jinda:/path/to/local/jinda
+      # - ~/mygem/jinda_adminlte:/path/to/local/jinda_adminlte
+    ports:
+      - "3000:3000"
+    depends_on:
+      - mongodb
+
+  mongodb:
+    image: mongo:latest
+    container_name: jinda_mongodb_web
+    ports:
+      - "27017:27017"
+    volumes:
+      - mongodb_data_web:/data/db
+    environment:
+      - MONGO_INITDB_DATABASE=jinda_development
+
+volumes:
+  mongodb_data_web:

data/test/dummy/docker-compose.yml

@@ -1,21 +1,13 @@
-version: '3.5'
 services:
-  web:
-    build: .
-    env_file: .env
-    command: bash -c "rm -f tmp/pids/server.pid && bundle exec rails s -p 3000 -b '0.0.0.0'"
-    volumes:
-      - .:/myapp
-    ports:
-      - "3000:3000"
-    depends_on:
-      - mongodb
-
   mongodb:
-    image: mongo
+    image: mongo:latest
+    container_name: jinda_mongodb
     ports:
-      - "27888:27017"
-#     volumes:
-#       - type: bind
-#         source: ~/data
-#         target: ~/data/db
+      - "27017:27017"
+    volumes:
+      - mongodb_data:/data/db
+    environment:
+      - MONGO_INITDB_DATABASE=jinda_development
+
+volumes:
+  mongodb_data: