저는 이번 기말 프로젝트를 앱스미스 튜토리얼로 진행하였습니다. 저는 좋은 오픈소스에 대해서 찾아보고 있던 중 도커에서 1,000만회 이상 다운로드되었고, 깃허브에서 27000개 이상의 별을 받은 앱스미스를 발견하였습니다. 앱스미스에 대해 알아본 결과 앱스미스는 로우코드 프레임워크로 제한된 개발 지식을 가진 사용자들도 쉽게 접근할 수 있으며, 소프트웨어 개발의 장벽과 비용을 줄일 수 있는 강력한 도구였습니다. 따라서 저는 앱스미스를 이번 프로젝트 주제로 선정하게 되었고 이번 영상 강의 프로젝트를 통해 대학생들과 기업체 개발자들에게 앱스미스 플랫폼의 사용 방법과 효과를 알리고, 원활한 어플리케이션 개발 환경을 제공하고자 한다는 동기로 진행하였습니다.
동영상 강의에서는 앱스미스를 활용하여 간단한 도서관 시나리오를 구현하였습니다. 실습의 목표는 앱스미스를 사용하여 데이터 조회와 수정이 가능한 페이지를 만들어보는 것이었습니다. 강의에서 사용된 데이터는 Book Table과 User Table로 저의 깃허브(https://github.com/womok2/AppSmith)에서 다운로드할 수 있도록 하였습니다. BookTable은 캐글의 Book Recommendation Dataset을 참고하여 수정하여 만든 것입니다. Book Recommendation Dataset은 Public domain 라이센스이기 때문에 제가 이번 프로젝트에 쓰일 수 있게 조금 수정을 한 후 올렸습니다.
## Getting started
강의에서 진행된 과정은 다음과 같습니다.
To make it easy for you to get started with GitLab, here's a list of recommended next steps.
1. 앱스미스에 대한 간단한 소개 및 실습 도구 준비
2. 앱스미스 로그인 및 신규 어플리케이션 생성
3. 페이지 구성 요소 만들기 (테이블, 폼, 버튼 등)
4. 'Book'과 'User' 테이블에 데이터 연결 및 화면 구성
5. 책 대여와 관련된 데이터 수정 및 갱신 작업 시연
Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
## Add your files
-[ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
-[ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
-[ ] [Set up project integrations](https://git.ajou.ac.kr/womok2/FOSS2023-1_final/-/settings/integrations)
## Collaborate with your team
-[ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
-[ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
-[ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
-[ ] [Automatically merge when pipeline succeeds](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
## Test and Deploy
Use the built-in continuous integration in GitLab.
-[ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
-[ ] [Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
-[ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
-[ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
-[ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
***
# Editing this README
When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thank you to [makeareadme.com](https://www.makeareadme.com/) for this template.
## Suggestions for a good README
Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
## Name
Choose a self-explaining name for your project.
## Description
Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
## Badges
On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
## Visuals
Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
## Installation
Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
## Usage
Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
## Support
Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
## Roadmap
If you have ideas for releases in the future, it is a good idea to list them in the README.
## Contributing
State if you are open to contributions and what your requirements are for accepting them.
For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
## Authors and acknowledgment
Show your appreciation to those who have contributed to the project.
## License
For open source projects, say how it is licensed.
## Project status
If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
저는 앱스미스 튜토리얼에 대한 강의를 준비하면서 오류 발생했을 때 해결하기 어려웠다는 문제가 있었습니다. 그 이유는 국내에서 앱스미스에 대한 정보와 문제해결 사례가 부족하였기 때문이었습니다. 따라서 직접 문제를 해결하는데 앱스미스에 대한 유튜브나 해외 커뮤니티를 방문하는 등의 많은 시간과 노력이 소요되었다는 어려움이 있었습니다. 하지만 이번 앱스미스 튜토리얼을 진행하면서, 저는 앱스미스에 대한 지식과 경험을 더욱 쌓아가는 기회가 되었습니다. 이번 경험을 바탕으로 앱스미스를 이용한 새로운 웹프로젝틀를 구상중에 있습니다. 또한, 다양한 사용자들에게 앱스미스 사용 방법과 효용성을 전달하는 데 기여할 수 있게 된 것 같아 보람이 느껴졌습니다.
