jameshwadedow commited on
Commit
96db5d4
Β·
1 Parent(s): d6cef6f

[docs] update readme and gitignore

Browse files
Files changed (2) hide show
  1. .gitignore +160 -0
  2. README.md +37 -8
.gitignore CHANGED
@@ -2,3 +2,163 @@
2
  .venv/
3
  __pycache__
4
  .DS_Store
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
2
  .venv/
3
  __pycache__
4
  .DS_Store
5
+ # Byte-compiled / optimized / DLL files
6
+ __pycache__/
7
+ *.py[cod]
8
+ *$py.class
9
+
10
+ # C extensions
11
+ *.so
12
+
13
+ # Distribution / packaging
14
+ .Python
15
+ build/
16
+ develop-eggs/
17
+ dist/
18
+ downloads/
19
+ eggs/
20
+ .eggs/
21
+ lib/
22
+ lib64/
23
+ parts/
24
+ sdist/
25
+ var/
26
+ wheels/
27
+ share/python-wheels/
28
+ *.egg-info/
29
+ .installed.cfg
30
+ *.egg
31
+ MANIFEST
32
+
33
+ # PyInstaller
34
+ # Usually these files are written by a python script from a template
35
+ # before PyInstaller builds the exe, so as to inject date/other infos into it.
36
+ *.manifest
37
+ *.spec
38
+
39
+ # Installer logs
40
+ pip-log.txt
41
+ pip-delete-this-directory.txt
42
+
43
+ # Unit test / coverage reports
44
+ htmlcov/
45
+ .tox/
46
+ .nox/
47
+ .coverage
48
+ .coverage.*
49
+ .cache
50
+ nosetests.xml
51
+ coverage.xml
52
+ *.cover
53
+ *.py,cover
54
+ .hypothesis/
55
+ .pytest_cache/
56
+ cover/
57
+
58
+ # Translations
59
+ *.mo
60
+ *.pot
61
+
62
+ # Django stuff:
63
+ *.log
64
+ local_settings.py
65
+ db.sqlite3
66
+ db.sqlite3-journal
67
+
68
+ # Flask stuff:
69
+ instance/
70
+ .webassets-cache
71
+
72
+ # Scrapy stuff:
73
+ .scrapy
74
+
75
+ # Sphinx documentation
76
+ docs/_build/
77
+
78
+ # PyBuilder
79
+ .pybuilder/
80
+ target/
81
+
82
+ # Jupyter Notebook
83
+ .ipynb_checkpoints
84
+
85
+ # IPython
86
+ profile_default/
87
+ ipython_config.py
88
+
89
+ # pyenv
90
+ # For a library or package, you might want to ignore these files since the code is
91
+ # intended to run in multiple environments; otherwise, check them in:
92
+ # .python-version
93
+
94
+ # pipenv
95
+ # According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
96
+ # However, in case of collaboration, if having platform-specific dependencies or dependencies
97
+ # having no cross-platform support, pipenv may install dependencies that don't work, or not
98
+ # install all needed dependencies.
99
+ #Pipfile.lock
100
+
101
+ # poetry
102
+ # Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
103
+ # This is especially recommended for binary packages to ensure reproducibility, and is more
104
+ # commonly ignored for libraries.
105
+ # https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
106
+ #poetry.lock
107
+
108
+ # pdm
109
+ # Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
110
+ #pdm.lock
111
+ # pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
112
+ # in version control.
113
+ # https://pdm.fming.dev/#use-with-ide
114
+ .pdm.toml
115
+
116
+ # PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
117
+ __pypackages__/
118
+
119
+ # Celery stuff
120
+ celerybeat-schedule
121
+ celerybeat.pid
122
+
123
+ # SageMath parsed files
124
+ *.sage.py
125
+
126
+ # Environments
127
+ .env
128
+ .venv
129
+ env/
130
+ venv/
131
+ ENV/
132
+ env.bak/
133
+ venv.bak/
134
+
135
+ # Spyder project settings
136
+ .spyderproject
137
+ .spyproject
138
+
139
+ # Rope project settings
140
+ .ropeproject
141
+
142
+ # mkdocs documentation
143
+ /site
144
+
145
+ # mypy
146
+ .mypy_cache/
147
+ .dmypy.json
148
+ dmypy.json
149
+
150
+ # Pyre type checker
151
+ .pyre/
152
+
153
+ # pytype static type analyzer
154
+ .pytype/
155
+
156
+ # Cython debug symbols
157
+ cython_debug/
158
+
159
+ # PyCharm
160
+ # JetBrains specific template is maintained in a separate JetBrains.gitignore that can
161
+ # be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
162
+ # and can be added to the global gitignore or merged into this file. For a more nuclear
163
+ # option (not recommended) you can uncomment the following to ignore the entire idea folder.
164
+ #.idea/
README.md CHANGED
@@ -1,6 +1,6 @@
1
  ---
2
- title: Shiny for Python template
3
- emoji: 🌍
4
  colorFrom: yellow
5
  colorTo: indigo
6
  sdk: docker
@@ -8,13 +8,42 @@ pinned: false
8
  license: apache-2.0
9
  ---
10
 
11
- This is a templated Space for [Shiny for Python](https://shiny.rstudio.com/py/).
12
 
 
13
 
14
- To get started with a new app do the following:
15
 
16
- 1) Install Shiny with `pip install shiny`
17
- 2) Create a new app with `shiny create .`
18
- 3) Then run the app with `shiny run --reload`
19
 
20
- To learn more about this framework please see the [Documentation](https://shiny.rstudio.com/py/docs/overview.html).
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
  ---
2
+ title: Axolotl Launcher πŸš€
3
+ emoji: πŸ‰
4
  colorFrom: yellow
5
  colorTo: indigo
6
  sdk: docker
 
8
  license: apache-2.0
9
  ---
10
 
11
+ Note: This is filler text for now, but the app will be a fine-tuning app for Hugging Face models. It will allow users to easily fine-tune models on their own datasets using Hugging Face's infrastructure.
12
 
13
+ ## Getting Started with Your Fine-Tuning App on Hugging Face Spaces
14
 
15
+ Welcome to the fine-tuning app hosted on Hugging Face Spaces! This app leverages the power of Hugging Face's infrastructure to allow you to launch and fine-tune machine learning models easily. Below you'll find a guide to help you get started with using this app.
16
 
17
+ ### Step 1: Create a Hugging Face Account
 
 
18
 
19
+ Before you can use the app, you need to have a Hugging Face account. If you don't have one, please sign up at Hugging Face.
20
+
21
+ ### Step 2: Launch the App
22
+
23
+ Once you have an account, navigate to the app hosted on Hugging Face Spaces. You can create a new space for your project directly on your profile or your organization's profile
24
+
25
+ ### Step 3: Configure Your Job
26
+
27
+ In the app, you'll be able to configure your fine-tuning job. This includes selecting the dataset, model, and fine-tuning parameters. If you're not sure about the configurations, the app provides guidance to help you make the best choices for your specific use case.
28
+
29
+ ### Step 4: Start Fine-Tuning
30
+
31
+ With your job configured, you can launch the fine-tuning process. The app will create a new space where your job will run. You can monitor the progress directly within the app.
32
+
33
+ ### Step 5: Job Completion and Shutdown
34
+
35
+ Once the training is complete, the job will automatically shut down. You don't need to worry about stopping the resources manually, as the app handles this for you
36
+
37
+ ### Step 6: Review and Download Results
38
+
39
+ After the job has finished, you can review the results and download any artifacts, such as the fine-tuned model. These will be available in the space created for your job.
40
+
41
+ ### Additional Information
42
+
43
+ Support: If you need help with making a Space or run into any issues, feel free to ask questions on the Hugging Face forum
44
+
45
+ Upgrades: You can upgrade your Space to run on a GPU or other accelerated hardware if your job requires it.
46
+ Persistent Storage: If your fine-tuning job requires persistent storage, this can be configured in your Space settings
47
+ Collaboration: You can work collaboratively with other people in the ML ecosystem by sharing your Space or inviting others to contribute.
48
+ Conclusion
49
+ This app is designed to make machine learning more accessible by simplifying the process of launching and fine-tuning models. We hope this guide helps you get started smoothly. Happy fine-tuning!