Skip to content

Commit

Permalink
Merge 2b89dc9 into 05818bb
Browse files Browse the repository at this point in the history
  • Loading branch information
kaladay committed Aug 19, 2022
2 parents 05818bb + 2b89dc9 commit 67ad58f
Show file tree
Hide file tree
Showing 4 changed files with 147 additions and 90 deletions.
84 changes: 60 additions & 24 deletions .gitignore
Original file line number Diff line number Diff line change
@@ -1,34 +1,70 @@
# Java project type gitignore
### Git ###
!.gitkeep

# Compiled class file
*.class

# Log file
*.log
### STS ###
.apt_generated
.classpath
.factorypath
.project
.settings
.springBeans
.sts4-cache

# BlueJ files
*.ctxt

# Mobile Tools for Java (J2ME)
.mtj.tmp/
### IntelliJ IDEA ###
.idea
*.iws
*.iml
*.ipr

# Package Files #
*.jar
*.war
*.nar
*.ear
*.zip
*.tar.gz
*.rar

# virtual machine crash logs, see http://www.java.com/en/download/help/error_hotspot.xml
hs_err_pid*
replay_pid*
### NetBeans ###
/nbproject/private/
/nbbuild/
/dist/
/nbdist/

# Docker gitignore
/.nb-gradle/


### VS Code ###
.vscode/

dump.rdb

# Application specific gitignore
# Maven
target/

### OS Specific ###
.DS_Store
.tmp/

tmp/


### Maven ###
logs/
target/

.classpth
.mvn/timing.properties
.mvn/wrapper/maven-wrapper.jar
.project

buildNumber.properties
dependency-reduced-pom.xml
pom.xml.next
pom.xml.tag
pom.xml.releaseBackup
pom.xml.versionsBackup
release.properties


### Weaver ###
dist/


### Project Specific ###
.env*

!**/src/main/**
!**/src/test/**
21 changes: 11 additions & 10 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -1,23 +1,23 @@
<a name="readme-top"></a>
# Contributing To ProjectManagementService
# Contributing to Project Management UI

Though ProjectManagementService is developed and maintained by Texas A&M University Libraries, we welcome community contributions.
Involvement in ProjectManagementService can take many forms:
Though *Project Management UI* is developed and maintained by Texas A&M University Libraries, we welcome community contributions.
Involvement in *Project Management UI* can take many forms.

<div align="right">(<a href="#readme-top">back to top</a>)</div>


## Using

Deploying ProjectManagementService and trying it out at your own institution is itself a way of contributing to the development process.
Deploying *Project Management UI* and trying it out at your own institution is itself a way of contributing to the development process.
For more information on deployment strategies please see the [Deployment Guide][deployment-guide].

[deployment-guide]: DEPLOYING.md

<div align="right">(<a href="#readme-top">back to top</a>)</div>


## Filing Issues

Once you are using ProjectManagementService the creation of new issues through GitHub is a major method of contribution towards ProjectManagementService development.
Once you are using *Project Management UI* the creation of new issues through GitHub is a major method of contribution towards *Project Management UI* development.
Issues can be motivated by the discovery of a bug in the software, or by the desire to see either new features added or see changes to existing features.

There are two primary types of issues:
Expand All @@ -30,10 +30,11 @@ A **Feature** involves new functionality or behavior.

<div align="right">(<a href="#readme-top">back to top</a>)</div>


## Creating a Pull Request

Community code and documentation contributions are welcome and should take the form of a **GitHub Pull Request** (*PR*).
Each *PR* will need to be reviewed by a ProjectManagementService developer.
Each *PR* will need to be reviewed by a *Project Management UI* developer.
A review will result in the *PR* being accepted and merged, a descriptive request for changes, or the *PR* being closed along with a detailed explanation.

It is our intention to maintain labeling on issues that are deemed to be low difficulty in order to provide a good point of entry for those looking to begin contributing code or documentation.
Expand All @@ -50,14 +51,14 @@ In general keep in mind:

<div align="right">(<a href="#readme-top">back to top</a>)</div>


## Good Luck!

We look forward to seeing your contributions.
If you have any additional questions please contact the ProjectManagementService developers at [helpdesk@library.tamu.edu][helpdesk-email].
If you have any additional questions please contact the *Project Management UI* developers at helpdesk@library.tamu.edu.

<div align="right">(<a href="#readme-top">back to top</a>)</div>

<!-- LINKS -->
[deployment-guide]: DEPLOYING.md
[semantic-versioning]: https://semver.org/
[helpdesk-email]: mailto:helpdesk@library.tamu.edu
120 changes: 67 additions & 53 deletions DEPLOYING.md
Original file line number Diff line number Diff line change
@@ -1,53 +1,67 @@
<a name="readme-top"></a>
# Deployment Guide

## Production Deployments

For **production** deployments, deploy using `docker-compose` via the [MyLibrary App][app-repo].
This is the recommended method of deployment for production systems.
Go to the [MyLibrary App][app-repo] and following the deployment instructions there.

Performing the deployment using the [MyLibrary App][app-repo] should be something similar to the following:
```shell
docker-compose up
```

The **development** deployment can also use `docker-compose` in the same way.

<div align="right">(<a href="#readme-top">back to top</a>)</div>


## Development Deployment using **Docker**

To manually use `docker` rather than `docker-compose`, run the following:

```shell
docker image build -t service .
docker run -it service
```

```
docker build --help
# -t, --tag list Name and optionally a tag in the
```

```
docker run --help
# -i, --interactive Keep STDIN open even if not attached.
# -t, --tty Allocate a pseudo-TTY
```

<div align="right">(<a href="#readme-top">back to top</a>)</div>

## Development Deployment using **Maven**

Running locally is easiest using spring boot:

```shell
mvn spring-boot:run
```

<div align="right">(<a href="#readme-top">back to top</a>)</div>

<!-- LINKS -->
[app-repo]: https://github.com/TAMULib/MyLibrary
<a name="readme-top"></a>
# Project Management Service Deployment Guide

## Production Deployments

For **production** deployments, deploy using `docker-compose` via the [Project App Repo][app-repo].
This is the recommended method of deployment for production systems.
Go to the [Project Management App Repo][app-repo] and following the deployment instructions there.

Performing the deployment using the [Project Management App Repo][app-repo] should be something similar to the following:
```shell
docker-compose up
```

The **development** deployment can also use `docker-compose` in the same way.

<div align="right">(<a href="#readme-top">back to top</a>)</div>


## Development Deployment using Docker

To manually use `docker` rather than `docker-compose`, run the following:

```shell
docker image build -t projectservice .
docker run -it projectservice
```

<sub>_* Note: `-t projectservice` and `-it projectservice` may be changed to another tag name as desired, such as `-t developing_on_this` and `-it developing_on_this`._</sub><br>

<div align="right">(<a href="#readme-top">back to top</a>)</div>


## Development Deployment using Maven

Manual deployment can be summed up by running:

```shell
mvn spring-boot:run
```

Those steps are a great way to start but they also fail to explain the customization that is often needed.
There are multiple ways to further configure this for deployment to better meet the desired requirements.

It is highly recommended only to perform *manual installation* when developing.
For **production** deployment, please use `docker-compose` via the [Project Management App Repo][app-repo] or use the **Docker** method above.

<div align="right">(<a href="#readme-top">back to top</a>)</div>


### Directly Configuring the `src/main/resources/application.yml` File

This method of configuration works by altering the configuration file.

With this in mind, the deployment steps now look like:

```shell
# Edit 'src/main/resources/application.yml' here.

mvn spring-boot:run
```

<div align="right">(<a href="#readme-top">back to top</a>)</div>


<!-- LINKS -->
[app-repo]: https://github.com/TAMULib/ProjectManagement
12 changes: 9 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,9 +1,11 @@
[![Build Status][build-badge]][build-status]
[![Coverage Status][coverage-badge]][coverage-status]

# Product Management Service
# Project Management Service

A service designed to connect our Library Service Status System to VersionOne and GitHub developed and maintained by [Texas A&M University Libraries][tamu-library].
A *Spring* backend for the *Project Management Service* developed and maintained by [Texas A&M University Libraries][tamu-library].

This is a service designed to interconnect our *Library Service Status System* with *VersionOne* and *GitHub* Services.

<details>
<summary>Table of contents</summary>
Expand All @@ -14,6 +16,7 @@ A service designed to connect our Library Service Status System to VersionOne an

</details>


## Deployment

For a quick and easy deployment using `docker-compose` consider using the [Project Managment App Repo][app-repo].
Expand All @@ -23,6 +26,7 @@ This process is further described in the [Deployment Guide][deployment-guide].

<div align="right">(<a href="#readme-top">back to top</a>)</div>


## Developer Documentation

- [Contributors Documentation][contribute-guide]
Expand All @@ -31,15 +35,17 @@ This process is further described in the [Deployment Guide][deployment-guide].

<div align="right">(<a href="#readme-top">back to top</a>)</div>


## Additional Resources

Please feel free to file any issues concerning Project Management Service to the issues section of the repository.

Any questions concerning Project Management Service can be directed to helpdesk@library.tamu.edu.

Copyright © 2022 Texas A&M University Libraries under the [MIT License][license].

<div align="right">(<a href="#readme-top">back to top</a>)</div>

Copyright © 2022 Texas A&M University Libraries under the [The MIT License][license].

<!-- LINKS -->
[app-repo]: https://github.com/TAMULib/ProjectManagement
Expand Down

0 comments on commit 67ad58f

Please sign in to comment.