تنظیمات¶
بررسی اجمالی¶
تنظیمات به شما امکان می‌دهد پیکربندی پروژه خود را مدیریت کنید.
نام پروژه¶
نام پروژه شما.
This defines the address that will be used to access your production database.
Addresses of your staging and development builds are derived from this name and assigned automatically. However, when you change your project name, only future builds will use the new name.
همکاران¶
کاربران Github را که می‌توانند به پروژه شما دسترسی داشته باشند را مدیریت کنید.
سه سطح کاربر وجود دارد:
Admin: has access to all features of an Odoo.sh project.
Tester: has access to the Staging and Development databases and their tooling. This role is for users conducting User Acceptance Tests. Testers can work with copies of production data but cannot access the production database through the Odoo.sh tooling.
Developer: has access only to the Development databases and their tooling. This role is for developers who propose code modifications but are not allowed to access production and staging databases through the Odoo.sh tooling.
Developer |
Tester |
Admin |
||
|---|---|---|---|---|
توسعه |
سوابق |
|||
1 روی اتصال کلیک کنید |
||||
سیاههها |
||||
Shell/SSH |
||||
نامه‌ها |
||||
تنظیمات |
||||
صحنه سازی |
سوابق |
|||
1 روی اتصال کلیک کنید |
||||
سیاههها |
||||
Shell/SSH |
||||
نامه‌ها |
||||
نظارت |
||||
پشتیبان گیری |
||||
ارتقا |
||||
تنظیمات |
||||
تولید |
سوابق |
|||
1 روی اتصال کلیک کنید |
||||
سیاههها |
||||
Shell/SSH |
||||
نامه‌ها |
||||
نظارت |
||||
پشتیبان گیری |
||||
ارتقا |
||||
تنظیمات |
||||
وضعیت |
||||
تنظیمات |
هشدار
Those roles only apply to the usage of Odoo.sh. It is important to reflect the user roles attribution within the repository on GitHub. Please refer to the GitHub documentation section on Managing a branch protection rule for detailed guidance.
دسترسی عمومی¶
اجازه دسترسی عمومی به بیلدهای توسعه خود را بدهید.
If activated, this option exposes the Builds page publicly, allowing visitors to view logs of development builds.
Production and staging builds are excluded, visitors can only see their status.
GitHub commit statuses¶
This option enables Odoo.sh to push commit statuses to your GitHub repository when a build is created or updated. It requires a GitHub token with permissions to push commit statuses to the repository. Refer to GitHub's documentation on personal access tokens for instructions to create yours.
توجه
GitHub's fine-grained personal tokens have an expiration date and will be disabled if they fail to update the commit status. You can replace the token at any time on Odoo.sh.
The commit statuses pushed to GitHub can have the following contexts:
ci/odoo.sh (dev): status of a development build
ci/odoo.sh (staging): status of a staging build
ci/odoo.sh (production): status of a production build
ci/odoo.sh (test_ci): testing the token from the Settings page will push a test status on the last commit of your repository
دامنه های سفارشی¶
To configure additional domains please refer to the corresponding branch's settings tab.
زیر ماژول ها¶
Configure the deploy keys for the private repositories you use as submodules in your branches to allow Odoo.sh to download them.
هشدار
These settings are required for private repositories only. If you are looking on how to set up your submodules, instructions are available in the chapter Submodules of this documentation.
When a repository is private, it is not possible to publicly download its branches and revisions. For that reason, you need to configure a deploy key for Odoo.sh, so the remote Git server allows our platform to download the revisions of this private repository.
برای پیکربندی کلید استقرار برای یک مخزن خصوصی، به صورت زیر عمل کنید:
in the input, paste the SSH URL of your private sub-repository and click on Add,
e.g. git@github.com:USERNAME/REPOSITORY.git
it can be another Git server than Github, such as Bitbucket, Gitlab or even your own self-hosted server
کلید عمومی را کپی کنید،
باید شبیه ssh-rsa چند...تصادفی...شخصیت...اینجا...== باشد
in the settings of the private sub-repository, add the public key amongst the deploy keys.
Github.com:
Bitbucket.com:
Gitlab.com:
Self-hosted: append the key to the git user’s authorized_keys file in its .ssh directory
اندازه ذخیره سازی¶
این بخش اندازه فضای ذخیره سازی مورد استفاده پروژه شما را نشان می‌دهد.
اندازه فضای ذخیره سازی به صورت زیر محاسبه می‌شود:
اندازه پایگاه داده PostgreSQL
the size of the disk files available in your container: database filestore, sessions storage directory...
هشدار
In case you want to analyze disk usage, you can run the tool ncdu in your Web Shell.
Should your production database size grow to exceed what's provisioned in your subscription, it will automatically be synchronized with it.
کارگران پایگاه داده¶
Additional database workers can be configured here. More workers help increase the load your production database is able to handle. If you add more, it will automatically be synchronized with your subscription.
هشدار
Adding more workers will not magically solve all performance issues. It only allows the server to handle more connections at the same time. If some operations are unusually slow, it's most likely a problem with the code, if it's not due to your own customizations you can open a ticket here.
شاخه های صحنه سازی¶
Additional staging branches allow you to develop and test more features at the same time. If you add more, it will automatically be synchronized with your subscription.
فعال‌سازی¶
Shows the status of the project's activation. You can change the project's activation code if needed.
