Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
schedules
schedules
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 11
    • Issues 11
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • SRCT
  • schedulesschedules
  • Issues
  • #27

Closed
Open
Opened Sep 24, 2018 by Zac Wood@zwood2Owner
  • Report abuse
  • New issue
Report abuse New issue

Update README with instructions for v2

Summary

The project structure is changing for Schedules v2. The current README has the old project structure of a separated web app and API, and it needs to be updated to explain the new project structure, which is a unified Rails app.

Update the README by doing the following:

  1. Get rid of instructions for setting up the Web app/client
  2. Change mentions of the schedules_api directory to just schedules, as that is the new directory name for the unified app
  3. Change mentions of "API" to "the project", since the schedules directory now contains both the API and website

Helpful Links

  • dev-v2 branch
  • Current README
To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
v2.0
Milestone
v2.0 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: srct/schedules#27