# SOME DESCRIPTIVE TITLE. # Copyright (C) Odoo S.A. # This file is distributed under the same license as the Odoo package. # FIRST AUTHOR , YEAR. # # Translators: # JH CHOI , 2023 # Martin Trigaux, 2023 # Wil Odoo, 2023 # Daye Jeong, 2024 # Sarah Park, 2024 # #, fuzzy msgid "" msgstr "" "Project-Id-Version: Odoo 16.0\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2024-01-19 08:39+0000\n" "PO-Revision-Date: 2023-01-13 14:30+0000\n" "Last-Translator: Sarah Park, 2024\n" "Language-Team: Korean (https://app.transifex.com/odoo/teams/41243/ko/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Language: ko\n" "Plural-Forms: nplurals=1; plural=0;\n" #: ../../content/administration.rst:8 msgid "Install and Maintain" msgstr "설치 및 유지관리" #: ../../content/administration.rst:10 msgid "" "These guides provide instructions on how to install, maintain and upgrade " "Odoo databases." msgstr "이 가이드에서는 Odoo 데이터베이스를 설치, 유지 관리 및 업그레이드하는 방법을 안내해 드립니다." #: ../../content/administration.rst:13 msgid "" ":doc:`History of Versions `" msgstr "" ":doc:`History of Versions `" #: ../../content/administration/install.rst:5 msgid "Install" msgstr "설치하기" #: ../../content/administration/install.rst:7 msgid "" "Depending on the intended use case, there are multiple ways to install Odoo " "- or not install it at all." msgstr "Odoo를 설치하는 방법은 사용 목적에 따라 여러 가지가 있으며, 아예 설치를 하지 않을 수도 있습니다." #: ../../content/administration/install.rst:10 msgid "" ":doc:`Online ` is the easiest way to use Odoo in production " "or to try it." msgstr ":doc:`Online <설치/온라인>`은 프로덕션 환경에서 Odoo를 사용하거나 시험해 볼 수 있는 가장 쉬운 방법입니다." #: ../../content/administration/install.rst:12 msgid "" ":doc:`Packaged installers ` are suitable for testing Odoo " "and developing modules. They can be used for long-term production with " "additional deployment and maintenance work." msgstr "" ":doc:`패키지 설치 프로그램 `은 Odoo 테스트 및 모듈 개발에 적합합니다. 프로덕션 환경에서 " "장기간 사용하려면 추가 배포 및 유지 관리 작업과 함께 사용할 수 있습니다." #: ../../content/administration/install.rst:16 msgid "" ":doc:`Source install ` provides greater flexibility, as it " "allows, for example, running multiple Odoo versions on the same system. It " "is adequate to develop modules and can be used as a base for production " "deployment." msgstr "" ":doc:`원본 설치 `옵션은 유연성이 향상되어 단일 시스템에서 여러 Odoo 버전을 실행하는 등의 작업을 " "수행할 수 있습니다. 모듈 개발에 적합하며 프로덕션 배포를 위한 기반으로 사용할 수 있습니다." #: ../../content/administration/install.rst:20 msgid "" "A `Docker `_ base image is available for " "development or deployment." msgstr "" "`도커 `_ 기본 이미지는 개발 및 배포 목적으로 사용할 수 있습니다." #: ../../content/administration/install.rst:26 msgid "Editions" msgstr "에디션" #: ../../content/administration/install.rst:28 msgid "There are two different editions." msgstr "두 가지 다른 에디션이 있습니다." #: ../../content/administration/install.rst:30 msgid "" "**Odoo Community** is the free and open-source version of the software, " "licensed under the `GNU LGPLv3 " "`_. It is the core upon " "which Odoo Enterprise is built." msgstr "" "**Odoo 커뮤니티**는 소프트웨어의 무료 오픈 소스 버전으로, `GNU LGPLv3 " "`_ 라이선스에 따라 운영됩니다. 이는 Odoo" " 엔터프라이즈를 구축하는 기반이 됩니다." #: ../../content/administration/install.rst:34 msgid "" "**Odoo Enterprise** is the shared source version of the software, giving " "access to more functionalities, including functional support, upgrades, and " "hosting. `Pricing `_ starts from one app " "free." msgstr "" "**Odoo 엔터프라이즈**는 소프트웨어의 공유 소스 버전으로, 기능 지원, 업그레이드, 호스팅 등의 추가 기능에 대한 액세스를 " "제공합니다. 가격 `_은 무료 앱으로 시작합니다." #: ../../content/administration/install.rst:39 msgid "" ":doc:`Switch from Community to Enterprise ` at any time" " (except for the source install)." msgstr "" ":doc:`커뮤니티에서 엔터프라이즈로 전환 `은 언제든지 가능합니다. (소스 설치 제외)" #: ../../content/administration/install/cdn.rst:3 msgid "Set up a content delivery network (CDN)" msgstr "콘텐츠 전송 네트워크 (CDN: content delivery network)를 설정합니다." #: ../../content/administration/install/cdn.rst:8 msgid "Deploying with KeyCDN" msgstr "KeyCDN으로 배포하기" #: ../../content/administration/install/cdn.rst:10 msgid "" "A :abbr:`CDN (Content Delivery Network)` or *content distribution network*, " "is a geographically distributed network of servers that provides high speed " "internet content. The :abbr:`CDN (Content Delivery Network)` provides quick," " high-quality content delivery for content-heavy websites." msgstr "" ":abbr:`CDN (콘텐츠 전송 네트워크)` 또는 *콘텐츠 배포 네트워크*는 지리적으로 분산된 서버 네트워크로, 빠른 인터넷 콘텐츠 " "전송을 제공합니다. CDN (콘텐츠 전송 네트워크)`은 빠르고 고품질의 콘텐츠 전송을 보장하며, 특히 콘텐츠가 많은 웹사이트에 " "유용합니다." #: ../../content/administration/install/cdn.rst:14 msgid "" "This document will guide you through the setup of a KeyCDN_ account with an " "Odoo powered website." msgstr "이 문서는 Odoo에서 제공하는 웹사이트를 위해 KeyCDN_ 계정을 설정하는 과정을 안내합니다." #: ../../content/administration/install/cdn.rst:17 msgid "Create a pull zone in the KeyCDN dashboard" msgstr "KeyCDN 현황판에서 전체 영역 생성하기" #: ../../content/administration/install/cdn.rst:19 msgid "" "On the KeyCDN dashboard, start by navigating to the :menuselection:`Zones` " "menu item on the left. On the form, give a value to the :guilabel:`Zone " "Name`, which will appear as part of the :abbr:`CDN (Content Delivery " "Network)`'s :abbr:`URL (Uniform Resource Locator)`. Then, set the " ":guilabel:`Zone Status` to :guilabel:`active` to engage the zone. For the " ":guilabel:`Zone Type` set the value to :guilabel:`Pull`, and then, finally, " "under the :guilabel:`Pull Settings`, enter the :guilabel:`Origin URL`— this " "address should be the full Odoo database :abbr:`URL (Uniform Resource " "Locator)`." msgstr "" "KeyCDN 현황판에서 왼쪽의 :menuselection:`영역` 메뉴 항목으로 이동하는 것으로 시작합니다. 양식에서 :abbr:`CDN" " (콘텐츠 전송 네트워크)`의 :abbr:`UR L(유니폼 리소스 로케이터)`의 일부로 표시될 :guilabel:`영역 이름` 에 값을 " "입력합니다. 그런 다음 :guilabel:`영역 상태`를 :guilabel:`활성`으로 설정하여 영역을 활성화합니다. " ":guilabel:`영역 유형`의 값을 :guilabel:`가져오기` 로 설정한 다음, 마지막으로 :guilabel:` 설정 가져오기` " "아래에 :guilabel:`원본 URL`을 입력합니다 (이 주소는 전체 Odoo 데이터베이스 :abbr:`URL (Uniform " "Resource Locator)`이어야 합니다)." #: ../../content/administration/install/cdn.rst:28 msgid "" "Use ``https://yourdatabase.odoo.com`` and replace the *yourdatabase* " "subdomain prefix with the actual name of the database. A custom :abbr:`URL " "(Uniform Resource Locator)` can be used, as well, in place of the Odoo " "subdomain that was provided to the database." msgstr "" "``https://yourdatabase.odoo.com``을 사용하고 *yourdatabase* 하위 도메인 접두사를 데이터베이스의 " "실제 이름으로 바꾸세요. 데이터베이스에 있는 Odoo 하위 도메인 대신에 사용자가 지정한 :abbr:`URL (Uniform " "Resource Locator)`을 사용할 수도 있습니다. " #: ../../content/administration/install/cdn.rst-1 msgid "KeyCDN's Zone configuration page." msgstr "KeyCDN의 영역 설정 페이지" #: ../../content/administration/install/cdn.rst:36 msgid "" "Under the :guilabel:`General Settings` heading below the zone form, click " "the :guilabel:`Show all settings` button to expand the zone options. This " "should be the last option on the page. After expanding the " ":guilabel:`General Settings` ensure that the :guilabel:`CORS` option is " ":guilabel:`enabled`." msgstr "" "영역 양식 아래의 :guilabel:`일반 설정` 제목 아래에 있는 :guilabel:`전체 설정 표시` 버튼을 클릭하여 영역 옵션을 " "펼치세요. 페이지에 있는 마지막 옵션이어야 합니다. :guilabel:`일반 설정`을 펼친 후에는 :guilabel:`CORS` 옵션이 " ":guilabel:`활성화`로 되어 있는지 확인하세요." #: ../../content/administration/install/cdn.rst:41 msgid "" "Next, scroll to the bottom of the zone configuration page and " ":guilabel:`Save` the changes. KeyCDN will indicate that the new zone will be" " deployed. This can take about 10 minutes." msgstr "" "다음으로는, 영역 구성 페이지 하단으로 스크롤을 내려서 변경 사항을 :guilabel:`저장`합니다. KeyCDN이 새로운 영역으로 " "배포될 것임을 표시합니다. 이 작업은 약 10분 정도 소요됩니다." #: ../../content/administration/install/cdn.rst-1 msgid "KeyCDN deploying the new Zone." msgstr "새로운 영역을 배포하는 KeyCDN" #: ../../content/administration/install/cdn.rst:49 msgid "" "A new :guilabel:`Zone URL` has been generated for your Zone, in this example" " it is ``pulltest-xxxxx.kxcdn.com``. This value will differ for each " "database." msgstr "" "영역에 대하여 새로 :guilabel:`영역 URL`이 생성되었습니다 (이 예시에서는 ``pulltest-" "xxxxx.kxcdn.com``). 데이터베이스마다 값이 다를 수 있습니다." #: ../../content/administration/install/cdn.rst:52 msgid "" "Copy this :guilabel:`Zone URL` to a text editor for later, as it will be " "used in the next steps." msgstr ":guilabel:`지역 URL`을 텍스트 에디터에 복사하여 다음 단계에서 사용할 수 있도록 합니다." #: ../../content/administration/install/cdn.rst:55 msgid "Configure the Odoo instance with the new zone" msgstr "새로운 영역으로 Odoo 인스턴스 환경 설정" #: ../../content/administration/install/cdn.rst:57 msgid "" "In the Odoo :guilabel:`Website` app, go to the :menuselection:`Settings` and" " then activate the :guilabel:`Content Delivery Network (CDN)` setting and " "copy/paste the :guilabel:`Zone URL` value from the earlier step into the " ":guilabel:`CDN Base URL` field. This field is only visible and configurable " "when :doc:`Developer Mode <../../applications/general/developer_mode>` is " "activated." msgstr "" "Odoo :guilabel:`웹사이트` 앱에서 :menuselection:`설정`으로 이동한 다음 :guilabel:`콘텐츠 전송 " "네트워크 (CDN)` 설정을 활성화하고 이전 단계의 :guilabel:`영역 URL` 값을 :guilabel:`CDN 기본 URL` " "필드에 복사/붙여넣기합니다. 이 필드는 :doc:`개발자 모드 " "<../../applications/general/developer_mode>`가 활성화된 경우에만 확인 및 환경 설정할 수 있습니다." #: ../../content/administration/install/cdn.rst:63 msgid "" "Ensure that there are two *forward slashes* (`//`) before the :guilabel:`CDN" " Base URL` and one forward slash (`/`) after the :guilabel:`CDN Base URL`." msgstr "" ":guilabel:`CDN Base URL` 앞에 *왼쪽 방향 슬래시*가 두 개 (`//`)있고 :guilabel:`CDN Base " "URL` 뒤에는 왼쪽 방향으로 슬래시가 하나 (`/`)가 있는지 확인합니다." #: ../../content/administration/install/cdn.rst:66 msgid ":guilabel:`Save` the settings when complete." msgstr "설정 완료 후 :guilabel:`저장`합니다." #: ../../content/administration/install/cdn.rst-1 msgid "Activate the CDN setting in Odoo." msgstr "Odoo에서 CDN 설정을 활성화합니다." #: ../../content/administration/install/cdn.rst:72 msgid "" "Now the website is using the CDN for the resources matching the " ":guilabel:`CDN filters` regular expressions." msgstr "이제 웹사이트에서는 :guilabel:`CDN 필터` 정규식과 일치하는 리소스에 CDN을 사용하고 있습니다." #: ../../content/administration/install/cdn.rst:75 msgid "" "In the HTML of the Odoo website, the :abbr:`CDN (content delivery network)` " "integration is evidenced as working properly by checking the :abbr:`URL " "(Uniform Resource Locators)` of images. The *CDN Base URL* value can be seen" " by using your web browser's :guilabel:`Inspect` feature on the Odoo " "website. Look for it's record by searching within the :guilabel:`Network` " "tab inside of devtools." msgstr "" "Odoo 웹사이트의 HTML에서 이미지의 :abbr:`CDN (content delivery network)` 통합 여부는 이미지의 " ":abbr:`URL (Uniform Resource Locators)`을 확인하여 정상적으로 작동하는 것으로 확인됩니다. *CDN 기본 " "URL* 값은 웹 브라우저의 :guilabel:`체크하기` 기능을 사용하여 Odoo 웹사이트에서 확인할 수 있습니다. 개발자 도구 내 " ":guilabel:`네트워크` 탭에서 검색하여 해당 기록을 찾습니다." #: ../../content/administration/install/cdn.rst-1 msgid "" "The CDN Base URL can be seen using the inspect function on the Odoo website." msgstr "CDN 기본 URL은 Odoo 웹사이트의 검사 기능을 사용하면 확인할 수 있습니다." #: ../../content/administration/install/cdn.rst:85 msgid "" "Prevent security issues by activating cross-origin resource sharing (CORS)" msgstr "교차 출처 리소스 공유 (CORS:Cross-Origin Resource Sharing)를 활성화하여 보안 문제 방지" #: ../../content/administration/install/cdn.rst:87 msgid "" "A security restriction in some browsers (such as Mozilla Firefox and Google " "Chrome) prevents a remotely linked CSS file to fetch relative resources on " "this same external server." msgstr "" "일부 브라우저 (예: Mozilla Firefox 및 Google Chrome)에서는 보안 제한으로 인해 원격으로 연결된 CSS 파일이 " "동일한 외부 서버에서 관련 리소스를 가져오는 것을 금지하고 있습니다." #: ../../content/administration/install/cdn.rst:90 msgid "" "If the :abbr:`CORS (Cross-Origin Resource Sharing)` option isn't enabled in " "the :guilabel:`CDN Zone`, the more obvious resulting problem on a standard " "Odoo website will be the lack of *Font Awesome* icons because the font file " "declared in the *Font Awesome* CSS won't be loaded from the remote server." msgstr "" ":abbr:`CORS (Cross-Origin Resource Sharing)` 옵션이 :guilabel:`CDN 영역`에서 활성화되지 " "않은 경우, 더 큰 문제는 *Font Awesome* CSS에 선언된 글꼴 파일은 원격 서버에서 로드되지 않기 때문에 표준 Odoo " "웹사이트에서 *Font Awesome* 아이콘이 없게 된다는 것입니다. " #: ../../content/administration/install/cdn.rst:95 msgid "" "When these cross-origin resource issues occur, a security error message " "similar to the output below will appear in the web browser's developer " "console:" msgstr "" #: ../../content/administration/install/cdn.rst:98 msgid "" "``Font from origin 'http://pulltest-xxxxx.kxcdn.com' has been blocked from " "loading /shop:1 by Cross-Origin Resource Sharing policy: No 'Access-Control-" "Allow-Origin' header is present on the requested resource. Origin " "'http://yourdatabase.odoo.com' is therefore not allowed access.``" msgstr "" #: ../../content/administration/install/cdn.rst-1 msgid "Error message populated in the browser console." msgstr "" #: ../../content/administration/install/cdn.rst:106 msgid "" "Enabling the :abbr:`CORS (Cross-Origin Resource Sharing)` option in the " ":abbr:`CDN (Content Delivery Network)` settings fixes this issue." msgstr "" #: ../../content/administration/install/deploy.rst:3 msgid "System configuration" msgstr "시스템 환경 설정" #: ../../content/administration/install/deploy.rst:5 msgid "" "This document describes basic steps to set up Odoo in production or on an " "internet-facing server. It follows :doc:`installation <../install>`, and is " "not generally necessary for a development systems that is not exposed on the" " internet." msgstr "" #: ../../content/administration/install/deploy.rst:10 msgid "" "If you are setting up a public server, be sure to check our :ref:`security` " "recommendations!" msgstr "" #: ../../content/administration/install/deploy.rst:15 msgid "dbfilter" msgstr "dbfilter" #: ../../content/administration/install/deploy.rst:17 msgid "" "Odoo is a multi-tenant system: a single Odoo system may run and serve a " "number of database instances. It is also highly customizable, with " "customizations (starting from the modules being loaded) depending on the " "\"current database\"." msgstr "" "Odoo에서는 멀티 테넌트 시스템을 사용하여, 하나의 Odoo 시스템이 여러 개의 데이터베이스 인스턴스를 실행하고 서비스할 수 있습니다." " 또한 '현재의 데이터베이스'에 따라 (로드 중인 모듈부터) 사용자 지정을 할 수 있으므로 고도의 커스터마이징을 할 수 있습니다." #: ../../content/administration/install/deploy.rst:21 msgid "" "This is not an issue when working with the backend (web client) as a logged-" "in company user: the database can be selected when logging in, and " "customizations loaded afterwards." msgstr "" "로그인한 회사 사용자가 백엔드 (웹 클라이언트)로 작업할 때는 문제가 되지 않습니다. 로그인할 때 데이터베이스를 선택하고 나중에 " "커스터마이징 항목을 로드할 수 있기 때문입니다." #: ../../content/administration/install/deploy.rst:25 msgid "" "However it is an issue for non-logged users (portal, website) which aren't " "bound to a database: Odoo needs to know which database should be used to " "load the website page or perform the operation. If multi-tenancy is not used" " that is not an issue, there's only one database to use, but if there are " "multiple databases accessible Odoo needs a rule to know which one it should " "use." msgstr "" "그러나 문제가 되는 것은 로그인을 하지 않는 사용자 (포털, 웹사이트)로, 데이터베이스에 바인딩되지 않는 경우입니다: Odoo는 웹사이트" " 페이지를 로드하거나 작업을 수행하기 위해 어떤 데이터베이스를 사용해야 하는지 확인해야만 합니다. 멀티 테넌트를 사용하지 않는 경우에는 " "사용할 데이터베이스가 하나뿐이므로 문제가 되지 않지만, 액세스할 수 있는 데이터베이스가 여러 개 있는 경우에는 어떤 데이터베이스를 " "사용해야 하는지 알 수 있는 규칙이 필요합니다." #: ../../content/administration/install/deploy.rst:31 msgid "" "That is one of the purposes of :option:`--db-filter `:" " it specifies how the database should be selected based on the hostname " "(domain) that is being requested. The value is a `regular expression`_, " "possibly including the dynamically injected hostname (``%h``) or the first " "subdomain (``%d``) through which the system is being accessed." msgstr "" #: ../../content/administration/install/deploy.rst:37 msgid "" "For servers hosting multiple databases in production, especially if " "``website`` is used, dbfilter **must** be set, otherwise a number of " "features will not work correctly." msgstr "" "프로덕션 중에 서버에서 여러 데이터베이스를 호스팅하는 경우, 특히 '웹사이트'를 사용하는 경우에는 반드시 dbfilter를 **설정해야 " "하며, 그렇지 않으면 여러 기능이 제대로 작동하지 않습니다." #: ../../content/administration/install/deploy.rst:42 msgid "Configuration samples" msgstr "환경설정 샘플" #: ../../content/administration/install/deploy.rst:44 msgid "Show only databases with names beginning with 'mycompany'" msgstr "" #: ../../content/administration/install/deploy.rst:46 #: ../../content/administration/install/deploy.rst:58 #: ../../content/administration/install/deploy.rst:153 #: ../../content/administration/install/deploy.rst:280 msgid "in :ref:`the configuration file ` set:" msgstr "" #: ../../content/administration/install/deploy.rst:53 msgid "" "Show only databases matching the first subdomain after ``www``: for example " "the database \"mycompany\" will be shown if the incoming request was sent to" " ``www.mycompany.com`` or ``mycompany.co.uk``, but not for " "``www2.mycompany.com`` or ``helpdesk.mycompany.com``." msgstr "" #: ../../content/administration/install/deploy.rst:67 msgid "" "Setting a proper :option:`--db-filter ` is an " "important part of securing your deployment. Once it is correctly working and" " only matching a single database per hostname, it is strongly recommended to" " block access to the database manager screens, and to use the ``--no-" "database-list`` startup parameter to prevent listing your databases, and to " "block access to the database management screens. See also security_." msgstr "" "알맞은 :option:`--db-filter `를 설정하는 것이 배포 보안에 있어 중요한 " "부분입니다. 정확히 작동하고 호스트 이름당 데이터베이스가 하나만 일치하도록 하고 난 후, 데이터베이스 관리자 화면에 대한 액세스를 " "차단하고 ``--no-database-list`` 시작 매개변수를 사용하여 데이터베이스 목록이 표시되지 않도록 하고 데이터베이스 관리 " "화면에 대한 액세스를 차단하는 것이 좋습니다. 보안_ 항목도 참조하세요." #: ../../content/administration/install/deploy.rst:76 #: ../../content/administration/install/source.rst:189 msgid "PostgreSQL" msgstr "PostgreSQL" #: ../../content/administration/install/deploy.rst:78 msgid "" "By default, PostgreSQL only allows connection over UNIX sockets and loopback" " connections (from \"localhost\", the same machine the PostgreSQL server is " "installed on)." msgstr "" #: ../../content/administration/install/deploy.rst:82 msgid "" "UNIX socket is fine if you want Odoo and PostgreSQL to execute on the same " "machine, and is the default when no host is provided, but if you want Odoo " "and PostgreSQL to execute on different machines [#different-machines]_ it " "will need to `listen to network interfaces`_ [#remote-socket]_, either:" msgstr "" #: ../../content/administration/install/deploy.rst:87 msgid "" "Only accept loopback connections and `use an SSH tunnel`_ between the " "machine on which Odoo runs and the one on which PostgreSQL runs, then " "configure Odoo to connect to its end of the tunnel" msgstr "" #: ../../content/administration/install/deploy.rst:90 msgid "" "Accept connections to the machine on which Odoo is installed, possibly over " "ssl (see `PostgreSQL connection settings`_ for details), then configure Odoo" " to connect over the network" msgstr "" #: ../../content/administration/install/deploy.rst:95 #: ../../content/administration/install/deploy.rst:145 #: ../../content/administration/install/deploy.rst:235 #: ../../content/administration/install/deploy.rst:275 msgid "Configuration sample" msgstr "환경설정 샘플" #: ../../content/administration/install/deploy.rst:97 msgid "Allow tcp connection on localhost" msgstr "" #: ../../content/administration/install/deploy.rst:98 msgid "Allow tcp connection from 192.168.1.x network" msgstr "" #: ../../content/administration/install/deploy.rst:100 msgid "in ``/etc/postgresql//main/pg_hba.conf`` set:" msgstr "" "in ``/etc/postgresql//main/pg_hba.conf`` set:" #: ../../content/administration/install/deploy.rst:108 msgid "" "in ``/etc/postgresql//main/postgresql.conf`` set:" msgstr "" "in ``/etc/postgresql//main/postgresql.conf`` set:" #: ../../content/administration/install/deploy.rst:119 msgid "Configuring Odoo" msgstr "Odoo 환경 설정하기" #: ../../content/administration/install/deploy.rst:121 msgid "" "Out of the box, Odoo connects to a local postgres over UNIX socket via port " "5432. This can be overridden using :ref:`the database options " "` when your Postgres deployment is not " "local and/or does not use the installation defaults." msgstr "" #: ../../content/administration/install/deploy.rst:126 msgid "" "The :doc:`packaged installers ` will automatically create a new " "user (``odoo``) and set it as the database user." msgstr "" #: ../../content/administration/install/deploy.rst:129 msgid "" "The database management screens are protected by the ``admin_passwd`` " "setting. This setting can only be set using configuration files, and is " "simply checked before performing database alterations. It should be set to a" " randomly generated value to ensure third parties can not use this " "interface." msgstr "" "데이터베이스 관리 화면은 ``어드민 비밀번호`` 설정으로 보호합니다. 이 설정은 환경 설정 파일을 통해서만 설정을 할 수 있으며, " "데이터베이스를 변경하기 전에 간단한 확인 절차를 거칩니다. 제3자가 이 인터페이스를 사용할 수 없도록 무작위로 값을 생성하여 설정해야 " "합니다." #: ../../content/administration/install/deploy.rst:134 msgid "" "All database operations use the :ref:`database options " "`, including the database management " "screen. For the database management screen to work requires that the " "PostgreSQL user have ``createdb`` right." msgstr "" "데이터베이스 관리 화면 외 모든 데이터베이스 작업에서는 :ref:`데이터베이스 옵션 " "`을 사용합니다. 데이터베이스 관리 화면이 작동하려면 PostgreSQL " "사용자에게 ``createdb`` 권한이 있어야 합니다." #: ../../content/administration/install/deploy.rst:138 msgid "" "Users can always drop databases they own. For the database management screen" " to be completely non-functional, the PostgreSQL user needs to be created " "with ``no-createdb`` and the database must be owned by a different " "PostgreSQL user." msgstr "" "사용자는 언제든지 자신이 소유한 데이터베이스를 삭제할 수 있습니다. 데이터베이스 관리 화면이 완전히 작동하지 않게 하려면 ``no-" "createdb``로 PostgreSQL 사용자를 생성해야 하며, 해당 데이터베이스는 다른 PostgreSQL 사용자가 소유하고 있어야 " "합니다." #: ../../content/administration/install/deploy.rst:142 msgid "the PostgreSQL user *must not* be a superuser" msgstr "" #: ../../content/administration/install/deploy.rst:147 msgid "connect to a PostgreSQL server on 192.168.1.2" msgstr "" #: ../../content/administration/install/deploy.rst:148 msgid "port 5432" msgstr "포트 5432" #: ../../content/administration/install/deploy.rst:149 msgid "using an 'odoo' user account," msgstr "" #: ../../content/administration/install/deploy.rst:150 msgid "with 'pwd' as a password" msgstr "" #: ../../content/administration/install/deploy.rst:151 msgid "filtering only db with a name beginning with 'mycompany'" msgstr "" #: ../../content/administration/install/deploy.rst:168 msgid "SSL Between Odoo and PostgreSQL" msgstr "" #: ../../content/administration/install/deploy.rst:170 msgid "" "Since Odoo 11.0, you can enforce ssl connection between Odoo and PostgreSQL." " in Odoo the db_sslmode control the ssl security of the connection with " "value chosen out of 'disable', 'allow', 'prefer', 'require', 'verify-ca' or " "'verify-full'" msgstr "" #: ../../content/administration/install/deploy.rst:175 msgid "" "`PostgreSQL Doc `_" msgstr "" "`PostgreSQL 참조 문서 `_" #: ../../content/administration/install/deploy.rst:180 msgid "Builtin server" msgstr "" #: ../../content/administration/install/deploy.rst:182 msgid "" "Odoo includes built-in HTTP, cron, and live-chat servers, using either " "multi-threading or multi-processing." msgstr "" #: ../../content/administration/install/deploy.rst:185 msgid "" "The **multi-threaded** server is a simpler server primarily used for " "development, demonstrations, and its compatibility with various operating " "systems (including Windows). A new thread is spawned for every new HTTP " "request, even for long-lived connections such as websocket. Extra daemonic " "cron threads are spawned too. Due to a Python limitation (GIL), it doesn't " "make the best use of the hardware." msgstr "" "**멀티스레드** 서버는 개발, 데모 및 다양한 운영 체제 (Windows 포함)와의 호환하기 위해 주로 사용되는 좀 더 단순한 " "서버입니다. 웹소켓과 같이 장기적인 연결을 포함하여 모든 새로운 HTTP 요청에 대해 새로운 스레드가 생성됩니다. 추가 데몬 크론 " "스레드도 생성됩니다. 파이썬의 한계 (GIL)로 인해 하드웨어를 최대한 활용할 수 없습니다." #: ../../content/administration/install/deploy.rst:191 msgid "" "The multi-threaded server is the default server, also for docker containers." " It is selected by leaving the :option:`--workers ` " "option out or setting it to ``0``." msgstr "" #: ../../content/administration/install/deploy.rst:194 msgid "" "The **multi-processing** server is a full-blown server primarily used for " "production. It is not liable to the same Python limitation (GIL) on resource" " usage and hence makes the best use of the hardware. A pool of workers is " "created upon server startup. New HTTP requests are queued by the OS until " "there are workers ready to process them. An extra event-driven HTTP worker " "for the live chat is spawned on an alternative port. Extra cron workers are " "spawned too. A configurable process reaper monitors resource usage and can " "kill/restart failed workers." msgstr "" "**멀티프로세싱** 서버는 주로 프로덕션에 사용되는 전면적인 서버입니다. 이 서버는 리소스 사용에 대한 동일한 파이썬 제한 (GIL)의 " "적용을 받지 않으므로 하드웨어를 최대한 활용할 수 있습니다. 서버가 시작되면 작업자 풀이 생성됩니다. 새로운 HTTP 요청은 작업자가 " "처리할 준비가 될 때까지 OS에서 대기열에 대기합니다. 라이브 채팅용으로 추가 이벤트 기반 HTTP 작업자가 대체 포트에 스폰됩니다. " "추가로 크론 워커도 스폰됩니다. 구성할 수 있는 프로세스 리퍼는 리소스 사용량을 모니터링하고 실패한 워커를 종료/재시작할 수 있습니다." #: ../../content/administration/install/deploy.rst:201 msgid "" "The multi-processing server is opt-in. It is selected by setting the " ":option:`--workers ` option to a non-null integer." msgstr "" #: ../../content/administration/install/deploy.rst:205 msgid "" "Because it is highly customized for Linux servers, the multi-processing " "server is not available on Windows." msgstr "" #: ../../content/administration/install/deploy.rst:209 msgid "Worker number calculation" msgstr "작업자 수 계산" #: ../../content/administration/install/deploy.rst:211 msgid "Rule of thumb : (#CPU * 2) + 1" msgstr "" #: ../../content/administration/install/deploy.rst:212 msgid "Cron workers need CPU" msgstr "" #: ../../content/administration/install/deploy.rst:213 msgid "1 worker ~= 6 concurrent users" msgstr "" #: ../../content/administration/install/deploy.rst:216 msgid "memory size calculation" msgstr "메모리 크기 계산" #: ../../content/administration/install/deploy.rst:218 msgid "" "We consider 20% of the requests are heavy requests, while 80% are simpler " "ones" msgstr "" #: ../../content/administration/install/deploy.rst:219 msgid "" "A heavy worker, when all computed field are well designed, SQL requests are " "well designed, ... is estimated to consume around 1GB of RAM" msgstr "" #: ../../content/administration/install/deploy.rst:220 msgid "" "A lighter worker, in the same scenario, is estimated to consume around 150MB" " of RAM" msgstr "" #: ../../content/administration/install/deploy.rst:222 msgid "" "Needed RAM = #worker * ( (light_worker_ratio * light_worker_ram_estimation) " "+ (heavy_worker_ratio * heavy_worker_ram_estimation) )" msgstr "" #: ../../content/administration/install/deploy.rst:225 #: ../../content/administration/install/deploy.rst:412 msgid "LiveChat" msgstr "실시간 채팅" #: ../../content/administration/install/deploy.rst:227 msgid "" "In multi-processing, a dedicated LiveChat worker is automatically started " "and listens on the :option:`--gevent-port `. By " "default, the HTTP requests will keep accessing the normal HTTP workers " "instead of the LiveChat one. You must deploy a proxy in front of Odoo and " "redirect incoming requests whose path starts with ``/websocket/`` to the " "LiveChat worker. You must also start Odoo in :option:`--proxy-mode ` so it uses the real client headers (such as hostname, " "scheme, and IP) instead of the proxy ones." msgstr "" "멀티 프로세싱에서는, 전용 실시간 채팅 작업자가 자동으로 시작되어 :option:`--gevent-port `에서 수신 대기합니다. 기본적으로 HTTP 요청은 실시간 채팅이 아닌 일반 HTTP 워커에 계속 액세스합니다." " Odoo 앞에 프록시를 배포하고 경로가 ``/웹소켓/``으로 시작하는 수신 요청을 실시간 채팅 작업자로 이동시켜야 합니다. 또한 " "Odoo가 프록시 헤더 대신 실제 클라이언트 헤더 (예: 호스트 이름, 스키마 및 IP)를 사용하도록 :option:`--proxy-" "mode `에서 시작해야 합니다." #: ../../content/administration/install/deploy.rst:237 msgid "Server with 4 CPU, 8 Thread" msgstr "" #: ../../content/administration/install/deploy.rst:238 msgid "60 concurrent users" msgstr "" #: ../../content/administration/install/deploy.rst:240 msgid "60 users / 6 = 10 <- theoretical number of worker needed" msgstr "" #: ../../content/administration/install/deploy.rst:241 msgid "(4 * 2) + 1 = 9 <- theoretical maximal number of worker" msgstr "" #: ../../content/administration/install/deploy.rst:242 msgid "" "We'll use 8 workers + 1 for cron. We'll also use a monitoring system to " "measure cpu load, and check if it's between 7 and 7.5 ." msgstr "" #: ../../content/administration/install/deploy.rst:243 msgid "RAM = 9 * ((0.8*150) + (0.2*1024)) ~= 3Go RAM for Odoo" msgstr "" #: ../../content/administration/install/deploy.rst:245 msgid "in :ref:`the configuration file `:" msgstr "in :ref:`환경 설정 파일 `:" #: ../../content/administration/install/deploy.rst:261 msgid "HTTPS" msgstr "HTTPS" #: ../../content/administration/install/deploy.rst:263 msgid "" "Whether it's accessed via website/web client or web service, Odoo transmits " "authentication information in cleartext. This means a secure deployment of " "Odoo must use HTTPS\\ [#switching]_. SSL termination can be implemented via " "just about any SSL termination proxy, but requires the following setup:" msgstr "" #: ../../content/administration/install/deploy.rst:268 msgid "" "Enable Odoo's :option:`proxy mode `. This should only" " be enabled when Odoo is behind a reverse proxy" msgstr "" #: ../../content/administration/install/deploy.rst:269 msgid "Set up the SSL termination proxy (`Nginx termination example`_)" msgstr "" #: ../../content/administration/install/deploy.rst:270 msgid "Set up the proxying itself (`Nginx proxying example`_)" msgstr "" #: ../../content/administration/install/deploy.rst:271 msgid "" "Your SSL termination proxy should also automatically redirect non-secure " "connections to the secure port" msgstr "" #: ../../content/administration/install/deploy.rst:277 msgid "Redirect http requests to https" msgstr "" #: ../../content/administration/install/deploy.rst:278 msgid "Proxy requests to odoo" msgstr "" #: ../../content/administration/install/deploy.rst:286 msgid "in ``/etc/nginx/sites-enabled/odoo.conf`` set:" msgstr "in ``/etc/nginx/sites-enabled/odoo.conf`` set:" #: ../../content/administration/install/deploy.rst:361 msgid "HTTPS Hardening" msgstr "" #: ../../content/administration/install/deploy.rst:363 msgid "" "Add the `Strict-Transport-Security` header to all requests, in order to " "prevent browsers from ever sending a plain HTTP request to this domain. You " "will need to maintain a working HTTPS service with a valid certificate on " "this domain at all times, otherwise your users will see security alerts or " "be entirely unable to access it." msgstr "" #: ../../content/administration/install/deploy.rst:369 msgid "" "Force HTTPS connections during a year for every visitor in NGINX with the " "line:" msgstr "" #: ../../content/administration/install/deploy.rst:375 msgid "" "Additional configuration can be defined for the `session_id` cookie. The " "`Secure` flag can be added to ensure it is never transmitted over HTTP and " "`SameSite=Lax` to prevent authenticated `CSRF`_." msgstr "" #: ../../content/administration/install/deploy.rst:386 msgid "Odoo as a WSGI Application" msgstr "WSGI 응용 프로그램면에서의 Odoo" #: ../../content/administration/install/deploy.rst:388 msgid "" "It is also possible to mount Odoo as a standard WSGI_ application. Odoo " "provides the base for a WSGI launcher script as ``odoo-wsgi.example.py``. " "That script should be customized (possibly after copying it from the setup " "directory) to correctly set the configuration directly in " ":mod:`odoo.tools.config` rather than through the command-line or a " "configuration file." msgstr "" #: ../../content/administration/install/deploy.rst:394 msgid "" "However the WSGI server will only expose the main HTTP endpoint for the web " "client, website and webservice API. Because Odoo does not control the " "creation of workers anymore it can not setup cron or livechat workers" msgstr "" #: ../../content/administration/install/deploy.rst:399 msgid "Cron Workers" msgstr "" #: ../../content/administration/install/deploy.rst:401 msgid "" "Starting one of the built-in Odoo servers next to the WSGI server is " "required to process cron jobs. That server must be configured to only " "process crons and not HTTP requests using the :option:`--no-http ` cli option or the ``http_enable = False`` configuration file " "setting." msgstr "" #: ../../content/administration/install/deploy.rst:406 msgid "" "On Linux-like systems, using the multi-processing server over the multi-" "threading one is recommended to benefit from better hardware usage and " "increased stability, i.e., using the :option:`--workers=-1 ` and :option:`--max-cron-threads=n `" " cli options." msgstr "" #: ../../content/administration/install/deploy.rst:414 msgid "" "Using a gevent-compatible WSGI server is required for the correct operation " "of the live chat feature. That server should be able to handle many " "simultaneous long-lived connections but doesn't need a lot of processing " "power. All requests whose path starts with ``/websocket/`` should be " "directed to that server. A regular (thread/process-based) WSGI server should" " be used for all other requests." msgstr "" "실시간 채팅 기능이 올바르게 작동하게 하려면 gevent와 호환되는 WSGI 서버를 사용해야 합니다. 해당 서버는 지속 시간이 긴 다수 " "연결을 동시에 처리할 수 있어야 하지만 처리 능력이 많을 필요는 없습니다. 경로가 ``/websocket/``으로 시작하는 요청은 모두 " "해당 서버로 보내야 합니다. 다른 모든 요청에는 일반 (스레드/프로세스 기반) WSGI 서버를 사용해야 합니다." #: ../../content/administration/install/deploy.rst:420 msgid "" "The Odoo cron server can also be used to serve the live chat requests. Just " "drop the :option:`--no-http ` cli option from the cron " "server and make sure requests whose path starts with ``/websocket/`` are " "directed to this server, either on the :option:`--http-port ` (multi-threading server) or on the :option:`--gevent-port " "` (multi-processing server)." msgstr "" #: ../../content/administration/install/deploy.rst:429 msgid "Serving static files and attachments" msgstr "" #: ../../content/administration/install/deploy.rst:431 msgid "" "For development convenience, Odoo directly serves all static files and " "attachments in its modules. This may not be ideal when it comes to " "performances, and static files should generally be served by a static HTTP " "server." msgstr "" "개발 편의를 위해, Odoo에서는 모듈과 관련된 전체 정적 파일 및 첨부 파일을 직접 제공합니다. 이는 성능 측면에서는 이상적이지 않을 " "수 있으며, 정적 파일은 보통 정적 HTTP 서버를 통해 제공되어야 합니다." #: ../../content/administration/install/deploy.rst:436 msgid "Serving static files" msgstr "" #: ../../content/administration/install/deploy.rst:438 msgid "" "Odoo static files are located in each module's :file:`static/` folder, so " "static files can be served by intercepting all requests to " ":samp:`/{MODULE}/static/{FILE}`, and looking up the right module (and file) " "in the various addons paths." msgstr "" #: ../../content/administration/install/deploy.rst:442 msgid "" "It is recommended to set the ``Content-Security-Policy: default-src 'none'``" " header on all images delivered by the web server. It is not strictly " "necessary as users cannot modify/inject content inside of modules' " ":file:`static/` folder and existing images are final (they do not fetch new " "resources by themselves). However, it is good practice." msgstr "" #: ../../content/administration/install/deploy.rst:447 msgid "" "Using the above NGINX (https) configuration, the following ``map`` and " "``location`` blocks should be added to serve static files via NGINX." msgstr "" #: ../../content/administration/install/deploy.rst:474 msgid "" "The actual ``root`` and ``try_files`` directives are dependant on your " "installation, specifically on your :option:`--addons-path `." msgstr "" #: ../../content/administration/install/deploy.rst:481 msgid "Debian package" msgstr "" #: ../../content/administration/install/deploy.rst:483 msgid "" "Say Odoo has been installed via the **debian packages** for Community and " "Enterprise, and that the :option:`--addons-path ` is" " ``'/usr/lib/python3/dist-packages/odoo/addons'``." msgstr "" #: ../../content/administration/install/deploy.rst:487 #: ../../content/administration/install/deploy.rst:501 msgid "The ``root`` and ``try_files`` should be:" msgstr "" #: ../../content/administration/install/deploy.rst:494 msgid "Git sources" msgstr "" #: ../../content/administration/install/deploy.rst:496 msgid "" "Say Odoo has been installed via the **sources**, that both the Community and" " Enterprise git repositories were cloned in :file:`/opt/odoo/community` and " ":file:`/opt/odoo/enterprise` respectively, and that the :option:`--addons-" "path ` is " "``'/opt/odoo/community/odoo/addons,/opt/odoo/community/addons,/opt/odoo/enterprise'``." msgstr "" #: ../../content/administration/install/deploy.rst:509 msgid "Serving attachments" msgstr "" #: ../../content/administration/install/deploy.rst:511 msgid "" "Attachments are files stored in the filestore which access is regulated by " "Odoo. They cannot be directly accessed via a static web server as accessing " "them requires multiple lookups in the database to determine where the files " "are stored and whether the current user can access them or not." msgstr "" "첨부 파일이란 파일 저장소에 저장되어 있는 파일로, Odoo에서 액세스를 관리합니다. 첨부 파일에 액세스하려면 데이터베이스에서 파일이 " "저장된 위치와 현재 사용자가 해당 파일에 액세스할 수 있는지 여부를 확인하기 위해 여러 번 확인해야 하므로 정적 웹 서버를 통해 직접 " "액세스할 수 없습니다." #: ../../content/administration/install/deploy.rst:516 msgid "" "Nevertheless, once the file has been located and the access rights verified " "by Odoo, it is a good idea to serve the file using the static web server " "instead of Odoo. For Odoo to delegate serving files to the static web " "server, the `X-Sendfile `_ (apache) or " "`X-Accel " "`_ " "(nginx) extensions must be enabled and configured on the static web server. " "Once it is set up, start Odoo with the :option:`--x-sendfile ` CLI flag (this unique flag is used for both X-Sendfile and " "X-Accel)." msgstr "" "그러나, 일단 해당 파일을 확인하고 Odoo에서 액세스 권한이 승인된 후에는 Odoo보다는 스태틱 웹서버를 사용하여 파일을 제공하도록 " "하는 것이 좋습니다. Odoo에서 스태틱 웹서버로 해당 파일을 변경하려면, `X-Sendfile " "`_ (apache) 또는 `X-Accel " "`_ " "(nginx) 에 대해서 웹서버에서 확장 항목을 활성화하고 구성 설정을 실행해야 합니다. 설정이 완료되면, " ":option:`--x-sendfile ` CLI flag (해당 고유 플래그는 " "X-Sendfile and X-Accel 양쪽에서 사용됨) 로 Odoo를 실행합니다. " #: ../../content/administration/install/deploy.rst:526 msgid "" "The X-Sendfile extension for apache (and compatible web servers) does not " "require any supplementary configuration." msgstr "" #: ../../content/administration/install/deploy.rst:528 msgid "" "The X-Accel extension for NGINX **does** require the following additionnal " "configuration:" msgstr "" #: ../../content/administration/install/deploy.rst:537 msgid "" "In case you don't know what is the path to your filestore, start Odoo with " "the :option:`--x-sendfile ` option and navigate to " "the ``/web/filestore`` URL directly via Odoo (don't navigate to the URL via " "NGINX). This logs a warnings, the message contains the configuration you " "need." msgstr "" #: ../../content/administration/install/deploy.rst:546 msgid "Security" msgstr "보안" #: ../../content/administration/install/deploy.rst:548 msgid "" "For starters, keep in mind that securing an information system is a " "continuous process, not a one-shot operation. At any moment, you will only " "be as secure as the weakest link in your environment." msgstr "" "먼저, 정보 시스템 보안은 단발성 작업이 아니라 지속적인 과정이라는 점을 명심하시기 바랍니다. 어느 순간에, 보안 확보 수준이 환경에서의" " 가장 약한 고리의 수준으로 떨어질 수 있습니다." #: ../../content/administration/install/deploy.rst:552 msgid "" "So please do not take this section as the ultimate list of measures that " "will prevent all security problems. It's only intended as a summary of the " "first important things you should be sure to include in your security action" " plan. The rest will come from best security practices for your operating " "system and distribution, best practices in terms of users, passwords, and " "access control management, etc." msgstr "" "따라서 이 섹션에서 설명한 내용만으로 모든 보안 관련 문제를 방지하기 위한 궁극적인 조치로 판단하지 않으시기를 바랍니다. 이는 보안 작업" " 계획에 반드시 포함되어야 할 첫번째 중요 사항들을 요약한 내용에 불과합니다. 나머지 항목은 운영 체제 및 배포에 대한 최상의 보안 " "사례, 사용자 측면에서의 모범 사례, 암호 및 액세스 제어 관리 등에서 확인하시기 바랍니다." #: ../../content/administration/install/deploy.rst:558 msgid "" "When deploying an internet-facing server, please be sure to consider the " "following security-related topics:" msgstr "인터넷 연결 서버를 배포할 경우, 다음의 보안 관련 주제를 반드시 고려하시기 바랍니다:" #: ../../content/administration/install/deploy.rst:561 msgid "" "Always set a strong super-admin admin password, and restrict access to the " "database management pages as soon as the system is set up. See " ":ref:`db_manager_security`." msgstr "" #: ../../content/administration/install/deploy.rst:564 msgid "" "Choose unique logins and strong passwords for all administrator accounts on " "all databases. Do not use 'admin' as the login. Do not use those logins for " "day-to-day operations, only for controlling/managing the installation. " "*Never* use any default passwords like admin/admin, even for test/staging " "databases." msgstr "" #: ../../content/administration/install/deploy.rst:569 msgid "" "Do **not** install demo data on internet-facing servers. Databases with demo" " data contain default logins and passwords that can be used to get into your" " systems and cause significant trouble, even on staging/dev systems." msgstr "" #: ../../content/administration/install/deploy.rst:573 msgid "" "Use appropriate database filters ( :option:`--db-filter `) to restrict the visibility of your databases according to the " "hostname. See :ref:`db_filter`. You may also use :option:`-d ` " "to provide your own (comma-separated) list of available databases to filter " "from, instead of letting the system fetch them all from the database " "backend." msgstr "" #: ../../content/administration/install/deploy.rst:580 msgid "" "Once your ``db_name`` and ``db_filter`` are configured and only match a " "single database per hostname, you should set ``list_db`` configuration " "option to ``False``, to prevent listing databases entirely, and to block " "access to the database management screens (this is also exposed as the " ":option:`--no-database-list ` command-line " "option)" msgstr "" #: ../../content/administration/install/deploy.rst:586 msgid "" "Make sure the PostgreSQL user (:option:`--db_user `) is " "*not* a super-user, and that your databases are owned by a different user. " "For example they could be owned by the ``postgres`` super-user if you are " "using a dedicated non-privileged ``db_user``. See also " ":ref:`setup/deploy/odoo`." msgstr "" #: ../../content/administration/install/deploy.rst:591 msgid "" "Keep installations updated by regularly installing the latest builds, either" " via GitHub or by downloading the latest version from " "https://www.odoo.com/page/download or http://nightly.odoo.com" msgstr "" #: ../../content/administration/install/deploy.rst:595 msgid "" "Configure your server in multi-process mode with proper limits matching your" " typical usage (memory/CPU/timeouts). See also :ref:`builtin_server`." msgstr "" #: ../../content/administration/install/deploy.rst:598 msgid "" "Run Odoo behind a web server providing HTTPS termination with a valid SSL " "certificate, in order to prevent eavesdropping on cleartext communications. " "SSL certificates are cheap, and many free options exist. Configure the web " "proxy to limit the size of requests, set appropriate timeouts, and then " "enable the :option:`proxy mode ` option. See also " ":ref:`https_proxy`." msgstr "" "일반 텍스트 통신을 도청하지 못하도록 유효한 SSL 인증서로 HTTPS를 종료하도록 하는 웹 서버 배경에서 Odoo를 실행해 보세요. " "저렴하고 다양한 SSL 인증서 무료 옵션이 있습니다. 웹 프록시를 설정하여 요청 사이즈를 제한하고 시간 제한을 적절하게 설정한 다음 " ":option:`proxy mode ` 옵션을 활성화합니다. :ref:`https_proxy`도" " 참고해 보세요." #: ../../content/administration/install/deploy.rst:605 msgid "" "If you need to allow remote SSH access to your servers, make sure to set a " "strong password for **all** accounts, not just `root`. It is strongly " "recommended to entirely disable password-based authentication, and only " "allow public key authentication. Also consider restricting access via a VPN," " allowing only trusted IPs in the firewall, and/or running a brute-force " "detection system such as `fail2ban` or equivalent." msgstr "" #: ../../content/administration/install/deploy.rst:611 msgid "" "Consider installing appropriate rate-limiting on your proxy or firewall, to " "prevent brute-force attacks and denial of service attacks. See also " ":ref:`login_brute_force` for specific measures." msgstr "" #: ../../content/administration/install/deploy.rst:615 msgid "" "Many network providers provide automatic mitigation for Distributed Denial " "of Service attacks (DDOS), but this is often an optional service, so you " "should consult with them." msgstr "" #: ../../content/administration/install/deploy.rst:619 msgid "" "Whenever possible, host your public-facing demo/test/staging instances on " "different machines than the production ones. And apply the same security " "precautions as for production." msgstr "" #: ../../content/administration/install/deploy.rst:623 msgid "" "If your public-facing Odoo server has access to sensitive internal network " "resources or services (e.g. via a private VLAN), implement appropriate " "firewall rules to protect those internal resources. This will ensure that " "the Odoo server cannot be used accidentally (or as a result of malicious " "user actions) to access or disrupt those internal resources. Typically this " "can be done by applying an outbound default DENY rule on the firewall, then " "only explicitly authorizing access to internal resources that the Odoo " "server needs to access. `Systemd IP traffic access control " "`_ may also be useful to implement per-process network access " "control." msgstr "" "공개용 Odoo 서버가 민감한 내부 네트워크 리소스나 서비스에 액세스할 수 있는 경우 (예: 사설 VLAN을 통하는 경우), 해당 내부 " "리소스를 보호하기 위해 적절한 방화벽 규칙을 설정하세요. 이렇게 하면 실수로 (또는 악의적인 사용자 행동의 결과로) Odoo 서버가 해당" " 내부 리소스에 액세스하거나 중단시키는 데 사용되지 않도록 합니다. 일반적으로 방화벽에 아웃바운드 기본 거부 규칙을 적용한 다음 Odoo" " 서버가 액세스해야 하는 내부 리소스에 대한 액세스만 명시적으로 승인하면 됩니다. 시스템 IP 트래픽 액세스 제어 " "`_는 프로세스별 네트워크 액세스 제어 설정에 유용하게 사용할 수 있습니다." #: ../../content/administration/install/deploy.rst:634 msgid "" "If your public-facing Odoo server is behind a Web Application Firewall, a " "load-balancer, a transparent DDoS protection service (like CloudFlare) or a " "similar network-level device, you may wish to avoid direct access to the " "Odoo system. It is generally difficult to keep the endpoint IP addresses of " "your Odoo servers secret. For example they can appear in web server logs " "when querying public systems, or in the headers of emails posted from Odoo. " "In such a situation you may want to configure your firewall so that the " "endpoints are not accessible publicly except from the specific IP addresses " "of your WAF, load-balancer or proxy service. Service providers like " "CloudFlare usually maintain a public list of their IP address ranges for " "this purpose." msgstr "" "공개용 Odoo 서버가 웹 애플리케이션 방화벽, 로드 밸런서, 투명한 DDoS 보호 서비스 (예: CloudFlare) 또는 이와 유사한" " 네트워크 수준 장치 뒤에 있는 경우, Odoo 시스템에 직접 액세스하지 않는 것이 좋습니다. 보통 Odoo 서버의 엔드포인트 IP " "주소를 기밀로 유지되기는 쉽지 않습니다. 예를 들어 공용 시스템을 쿼리할 때 웹 서버 로그에 표시되거나 Odoo에서 게시된 이메일의 " "헤더에 표시될 수 있습니다. 이러한 상황에서는 WAF, 로드 밸런서 또는 프록시 서비스의 특정 IP 주소를 제외하고는 엔드포인트에 " "공개적으로 액세스할 수 없도록 방화벽을 구성하는 것을 추천합니다. CloudFlare와 같은 서비스 제공업체는 일반적으로 이러한 목적을 " "위해 공개 목록을 IP 주소 범위로 유지합니다." #: ../../content/administration/install/deploy.rst:645 msgid "" "If you are hosting multiple customers, isolate customer data and files from " "each other using containers or appropriate \"jail\" techniques." msgstr "" #: ../../content/administration/install/deploy.rst:648 msgid "" "Setup daily backups of your databases and filestore data, and copy them to a" " remote archiving server that is not accessible from the server itself." msgstr "" #: ../../content/administration/install/deploy.rst:651 msgid "" "Deploying Odoo on Linux is strongly recommended over Windows. Should you " "choose nevertheless to deploy on a Windows platform, a thorough security " "hardening review of the server should be conducted and is outside of the " "scope of this guide." msgstr "" "Windows보다는, Linux에서 Odoo를 배포하는 것을 강력히 권장합니다. 그럼에도 불구하고 Windows 플랫폼에서 배포하기로 " "선택한 경우에는 서버에 대한 철저한 보안 강화에 대해 검토해야 하며, 이는 본 가이드의 범위를 벗어나는 내용입니다." #: ../../content/administration/install/deploy.rst:659 msgid "Blocking Brute Force Attacks" msgstr "" #: ../../content/administration/install/deploy.rst:661 msgid "" "For internet-facing deployments, brute force attacks on user passwords are " "very common, and this threat should not be neglected for Odoo servers. Odoo " "emits a log entry whenever a login attempt is performed, and reports the " "result: success or failure, along with the target login and source IP." msgstr "" #: ../../content/administration/install/deploy.rst:665 msgid "The log entries will have the following form." msgstr "" #: ../../content/administration/install/deploy.rst:667 msgid "Failed login::" msgstr "" #: ../../content/administration/install/deploy.rst:671 msgid "Successful login::" msgstr "" #: ../../content/administration/install/deploy.rst:676 msgid "" "These logs can be easily analyzed by an intrusion prevention system such as " "`fail2ban`." msgstr "" #: ../../content/administration/install/deploy.rst:678 msgid "" "For example, the following fail2ban filter definition should match a failed " "login::" msgstr "" #: ../../content/administration/install/deploy.rst:685 msgid "" "This could be used with a jail definition to block the attacking IP on " "HTTP(S)." msgstr "" #: ../../content/administration/install/deploy.rst:687 msgid "" "Here is what it could look like for blocking the IP for 15 minutes when 10 " "failed login attempts are detected from the same IP within 1 minute::" msgstr "" #: ../../content/administration/install/deploy.rst:701 msgid "Database Manager Security" msgstr "" #: ../../content/administration/install/deploy.rst:703 msgid ":ref:`setup/deploy/odoo` mentioned ``admin_passwd`` in passing." msgstr "" #: ../../content/administration/install/deploy.rst:705 msgid "" "This setting is used on all database management screens (to create, delete, " "dump or restore databases)." msgstr "" #: ../../content/administration/install/deploy.rst:708 msgid "" "If the management screens must not be accessible at all, you should set " "``list_db`` configuration option to ``False``, to block access to all the " "database selection and management screens." msgstr "" #: ../../content/administration/install/deploy.rst:714 msgid "" "It is strongly recommended to disable the Database Manager for any internet-" "facing system! It is meant as a development/demo tool, to make it easy to " "quickly create and manage databases. It is not designed for use in " "production, and may even expose dangerous features to attackers. It is also " "not designed to handle large databases, and may trigger memory limits." msgstr "" "인터넷을 사용하는 전체 시스템에서 데이터베이스 관리자 비활성화를 실행할 것을 강력히 권장합니다! 데이터베이스 관리자는 데이터베이스를 쉽게" " 생성하고 관리할 수 있는 개발/데모 도구입니다. 프로덕션 환경에서 사용하도록 설계되지 않았으며, 공격자에게 위험한 기능을 노출시킬 수도" " 있습니다. 또한 대용량 데이터베이스를 처리하도록 설계되지 않았으며 메모리 제한을 유발할 수 있습니다." #: ../../content/administration/install/deploy.rst:720 msgid "" "On production systems, database management operations should always be " "performed by the system administrator, including provisioning of new " "databases and automated backups." msgstr "" #: ../../content/administration/install/deploy.rst:723 msgid "" "Be sure to setup an appropriate ``db_name`` parameter (and optionally, " "``db_filter`` too) so that the system can determine the target database for " "each request, otherwise users will be blocked as they won't be allowed to " "choose the database themselves." msgstr "" #: ../../content/administration/install/deploy.rst:728 msgid "" "If the management screens must only be accessible from a selected set of " "machines, use the proxy server's features to block access to all routes " "starting with ``/web/database`` except (maybe) ``/web/database/selector`` " "which displays the database-selection screen." msgstr "" #: ../../content/administration/install/deploy.rst:732 msgid "" "If the database-management screen should be left accessible, the " "``admin_passwd`` setting must be changed from its ``admin`` default: this " "password is checked before allowing database-alteration operations." msgstr "" #: ../../content/administration/install/deploy.rst:736 msgid "It should be stored securely, and should be generated randomly e.g." msgstr "" #: ../../content/administration/install/deploy.rst:742 msgid "which will generate a 32 characters pseudorandom printable string." msgstr "" #: ../../content/administration/install/deploy.rst:745 msgid "Supported Browsers" msgstr "" #: ../../content/administration/install/deploy.rst:747 msgid "" "Odoo supports all the major desktop and mobile browsers available on the " "market, as long as they are supported by their publishers." msgstr "" #: ../../content/administration/install/deploy.rst:750 msgid "Here are the supported browsers:" msgstr "" #: ../../content/administration/install/deploy.rst:752 msgid "Google Chrome" msgstr "" #: ../../content/administration/install/deploy.rst:753 msgid "Mozilla Firefox" msgstr "" #: ../../content/administration/install/deploy.rst:754 msgid "Microsoft Edge" msgstr "" #: ../../content/administration/install/deploy.rst:755 msgid "Apple Safari" msgstr "" #: ../../content/administration/install/deploy.rst:757 msgid "" "Please make sure your browser is up-to-date and still supported by its " "publisher before filing a bug report." msgstr "" #: ../../content/administration/install/deploy.rst:762 msgid "Since Odoo 13.0, ES6 is supported. Therefore, IE support is dropped." msgstr "" #: ../../content/administration/install/deploy.rst:765 msgid "" "to have multiple Odoo installations use the same PostgreSQL database, or to " "provide more computing resources to both software." msgstr "" #: ../../content/administration/install/deploy.rst:768 msgid "" "technically a tool like socat_ can be used to proxy UNIX sockets across " "networks, but that is mostly for software which can only be used over UNIX " "sockets" msgstr "" #: ../../content/administration/install/deploy.rst:772 msgid "" "or be accessible only over an internal packet-switched network, but that " "requires secured switches, protections against `ARP spoofing`_ and precludes" " usage of WiFi. Even over secure packet-switched networks, deployment over " "HTTPS is recommended, and possible costs are lowered as \"self-signed\" " "certificates are easier to deploy on a controlled environment than over the " "internet." msgstr "" #: ../../content/administration/install/email_gateway.rst:3 msgid "Email gateway" msgstr "" #: ../../content/administration/install/email_gateway.rst:5 msgid "" "The Odoo mail gateway allows you to inject directly all the received emails " "in Odoo." msgstr "" #: ../../content/administration/install/email_gateway.rst:7 msgid "" "Its principle is straightforward: your SMTP server executes the \"mailgate\"" " script for every new incoming email." msgstr "" #: ../../content/administration/install/email_gateway.rst:10 msgid "" "The script takes care of connecting to your Odoo database through XML-RPC, " "and send the emails via the `MailThread.message_process()` feature." msgstr "" #: ../../content/administration/install/email_gateway.rst:14 msgid "Prerequisites" msgstr "전제 조건" #: ../../content/administration/install/email_gateway.rst:16 msgid "Administrator access to the Odoo database." msgstr "" #: ../../content/administration/install/email_gateway.rst:17 msgid "Your own mail server such as Postfix or Exim." msgstr "" #: ../../content/administration/install/email_gateway.rst:18 msgid "Technical knowledge on how to configure an email server." msgstr "" #: ../../content/administration/install/email_gateway.rst:21 msgid "For Postfix" msgstr "" #: ../../content/administration/install/email_gateway.rst:23 msgid "In you alias config (:file:`/etc/aliases`):" msgstr "" #: ../../content/administration/install/email_gateway.rst:30 #: ../../content/administration/install/email_gateway.rst:45 msgid "Resources" msgstr "자원" #: ../../content/administration/install/email_gateway.rst:32 msgid "`Postfix `_" msgstr "" #: ../../content/administration/install/email_gateway.rst:33 msgid "`Postfix aliases `_" msgstr "" #: ../../content/administration/install/email_gateway.rst:34 msgid "`Postfix virtual `_" msgstr "" #: ../../content/administration/install/email_gateway.rst:38 msgid "For Exim" msgstr "" #: ../../content/administration/install/email_gateway.rst:47 msgid "`Exim `_" msgstr "" #: ../../content/administration/install/email_gateway.rst:50 msgid "" "If you don't have access/manage your email server, use :ref:`inbound " "messages `." msgstr "" #: ../../content/administration/install/geo_ip.rst:3 msgid "Geo IP" msgstr "" #: ../../content/administration/install/geo_ip.rst:6 msgid "This documentation only applies to On-premise databases." msgstr "" #: ../../content/administration/install/geo_ip.rst:9 msgid "Installation" msgstr "설치" #: ../../content/administration/install/geo_ip.rst:12 msgid "" "Please note that the installation depends on your computer's operating " "system and distribution. We will assume that a Linux operating system is " "being used." msgstr "" #: ../../content/administration/install/geo_ip.rst:18 msgid "Install `geoip2 `__ Python library" msgstr "" #: ../../content/administration/install/geo_ip.rst:20 msgid "" "Download the `GeoLite2 City database " "`_. You should end up with a" " file called ``GeoLite2-City.mmdb``" msgstr "" #: ../../content/administration/install/geo_ip.rst:25 msgid "Move the file to the folder ``/usr/share/GeoIP/``" msgstr "" #: ../../content/administration/install/geo_ip.rst:27 msgid "Restart the server" msgstr "서버 다시 시작" #: ../../content/administration/install/geo_ip.rst:30 msgid "" "If you can't/don't want to locate the geoip database in " "``/usr/share/GeoIP/``, you can use the ``--geoip-db`` option of the Odoo " "command line interface. This option takes the absolute path to the GeoIP " "database file and uses it as the GeoIP database. For example:" msgstr "" #: ../../content/administration/install/geo_ip.rst:39 msgid ":doc:`CLI documentation `." msgstr ":doc:`CLI 문서 `." #: ../../content/administration/install/geo_ip.rst:42 msgid "" "``GeoIP`` Python library can also be used. However this version is " "discontinued since January 1. See `GeoLite Legacy databases are now " "discontinued `_" msgstr "" #: ../../content/administration/install/geo_ip.rst:47 msgid "How to test GeoIP geolocation in your Odoo website" msgstr "" #: ../../content/administration/install/geo_ip.rst:49 msgid "Go to your website. Open the web page that you want to test ``GeoIP``." msgstr "웹사이트로 이동합니다. ``GeoIP``를 테스트할 웹페이지를 엽니다." #: ../../content/administration/install/geo_ip.rst:50 msgid "Choose :menuselection:`Customize --> HTML/CSS/JS Editor`." msgstr ":menuselection:`사용자 지정 --> HTML/CSS/JS 편집기`를 선택합니다." #: ../../content/administration/install/geo_ip.rst:51 msgid "Add the following piece of XML in the page :" msgstr "페이지에 다음 XML을 추가합니다:" #: ../../content/administration/install/geo_ip.rst:57 msgid "" "You should end up with a dictionary indicating the location of the IP " "address." msgstr "" #: ../../content/administration/install/geo_ip.rst:63 msgid "" "If the curly braces are empty ``{}``, it can be for any of the following " "reasons :" msgstr "" #: ../../content/administration/install/geo_ip.rst:65 msgid "" "The browsing IP address is the localhost (``127.0.0.1``) or a local area " "network one (``192.168.*.*``)" msgstr "" #: ../../content/administration/install/geo_ip.rst:67 msgid "" "If a reversed proxy is used, make sure to configure it correctly. See " ":option:`proxy mode `" msgstr "" #: ../../content/administration/install/geo_ip.rst:69 msgid "``geoip2`` is not installed or the GeoIP database file wasn't found" msgstr "" #: ../../content/administration/install/geo_ip.rst:70 msgid "The GeoIP database was unable to resolve the given IP address" msgstr "" #: ../../content/administration/install/online.rst:3 msgid "Online" msgstr "온라인" #: ../../content/administration/install/online.rst:5 msgid "" "Online instances are accessed using any web browser and do not require a " "local installation." msgstr "" #: ../../content/administration/install/online.rst:8 msgid "Demo" msgstr "데모" #: ../../content/administration/install/online.rst:10 msgid "" "To quickly try out Odoo, shared `demo `_ instances " "are available. No registration is required, but each instance only lives for" " a few hours." msgstr "" #: ../../content/administration/install/online.rst:14 #: ../../content/administration/maintain/domain_names.rst:166 #: ../../content/administration/maintain/domain_names.rst:236 #: ../../content/administration/maintain/supported_versions.rst:29 #: ../../content/administration/upgrade.rst:90 #: ../../content/administration/upgrade.rst:307 msgid "Odoo Online" msgstr "Odoo 온라인" #: ../../content/administration/install/online.rst:16 msgid "" "`Odoo Online `_ provides private instances which" " are fully managed and hosted by Odoo. It can be used for long-term " "production or to test Odoo thoroughly, including customizations that don't " "require code." msgstr "" #: ../../content/administration/install/online.rst:21 msgid "Odoo Online is incompatible with custom modules or the Odoo App Store." msgstr "" #: ../../content/administration/install/packages.rst:3 msgid "Packaged installers" msgstr "" #: ../../content/administration/install/packages.rst:5 msgid "" "Odoo provides packaged installers for Debian-based Linux distributions " "(Debian, Ubuntu, etc.), RPM-based Linux distributions (Fedora, CentOS, RHEL," " etc.), and Windows for the Community and Enterprise editions." msgstr "" #: ../../content/administration/install/packages.rst:9 msgid "" "Official **Community** nightly packages with all relevant dependency " "requirements are available on the `nightly server " "`_." msgstr "" #: ../../content/administration/install/packages.rst:13 msgid "Nightly packages may be difficult to keep up to date." msgstr "" #: ../../content/administration/install/packages.rst:15 msgid "" "Official **Community** and **Enterprise** packages can be downloaded from " "the `Odoo download page `_." msgstr "" #: ../../content/administration/install/packages.rst:19 msgid "" "It is required to be logged in as a paying customer or partner to download " "the Enterprise packages." msgstr "" #: ../../content/administration/install/packages.rst:25 #: ../../content/administration/install/source.rst:52 #: ../../content/administration/install/source.rst:125 #: ../../content/administration/install/source.rst:148 #: ../../content/administration/install/source.rst:170 #: ../../content/administration/install/source.rst:195 #: ../../content/administration/install/source.rst:224 #: ../../content/administration/install/source.rst:267 #: ../../content/administration/install/source.rst:380 #: ../../content/administration/install/source.rst:442 msgid "Linux" msgstr "" #: ../../content/administration/install/packages.rst:28 #: ../../content/administration/install/source.rst:116 msgid "Prepare" msgstr "" #: ../../content/administration/install/packages.rst:30 msgid "" "Odoo needs a `PostgreSQL `_ server to run " "properly." msgstr "" #: ../../content/administration/install/packages.rst:34 #: ../../content/administration/install/packages.rst:70 #: ../../content/administration/install/packages.rst:100 #: ../../content/administration/install/source.rst:274 msgid "Debian/Ubuntu" msgstr "" #: ../../content/administration/install/packages.rst:36 msgid "" "The default configuration for the Odoo 'deb' package is to use the " "PostgreSQL server on the same host as the Odoo instance. Execute the " "following command to install the PostgreSQL server:" msgstr "" #: ../../content/administration/install/packages.rst:44 #: ../../content/administration/install/packages.rst:80 #: ../../content/administration/install/packages.rst:132 msgid "Fedora" msgstr "" #: ../../content/administration/install/packages.rst:46 msgid "" "Make sure that the `sudo` command is available and well configured and, only" " then, execute the following command to install the PostgreSQL server:" msgstr "" #: ../../content/administration/install/packages.rst:57 #: ../../content/administration/install/source.rst:412 msgid "" "`wkhtmltopdf` is not installed through **pip** and must be installed " "manually in `version 0.12.6 " "`_ for it " "to support headers and footers. Check out the `wkhtmltopdf wiki " "`_ for more details on the " "various versions." msgstr "" #: ../../content/administration/install/packages.rst:63 msgid "Repository" msgstr "" #: ../../content/administration/install/packages.rst:65 msgid "" "Odoo S.A. provides a repository that can be used to install the " "**Community** edition by executing the following commands:" msgstr "" #: ../../content/administration/install/packages.rst:78 msgid "" "Use the usual `apt-get upgrade` command to keep the installation up-to-date." msgstr "" #: ../../content/administration/install/packages.rst:90 msgid "Currently, there is no nightly repository for the Enterprise edition." msgstr "" #: ../../content/administration/install/packages.rst:93 msgid "Distribution package" msgstr "" #: ../../content/administration/install/packages.rst:95 msgid "" "Instead of using the repository, packages for both the **Community** and " "**Enterprise** editions can be downloaded from the `Odoo download page " "`_." msgstr "" #: ../../content/administration/install/packages.rst:103 msgid "" "Odoo 16 'deb' package currently supports `Debian Buster " "`_ and `Ubuntu 18.04 " "`_ or above." msgstr "" #: ../../content/administration/install/packages.rst:107 msgid "" "Once downloaded, execute the following commands **as root** to install Odoo " "as a service, create the necessary PostgreSQL user, and automatically start " "the server:" msgstr "" #: ../../content/administration/install/packages.rst:117 msgid "" "The `python3-xlwt` Debian package, needed to export into the XLS format, " "does not exist in Debian Buster nor Ubuntu 18.04. If needed, install it " "manually with the following:" msgstr "" #: ../../content/administration/install/packages.rst:124 msgid "" "The `num2words` Python package - needed to render textual amounts - does not" " exist in Debian Buster nor Ubuntu 18.04, which could cause problems with " "the `l10n_mx_edi` module. If needed, install it manually with the following:" msgstr "" #: ../../content/administration/install/packages.rst:135 msgid "Odoo 16 'rpm' package supports Fedora 36." msgstr "" #: ../../content/administration/install/packages.rst:137 msgid "" "Once downloaded, the package can be installed using the 'dnf' package " "manager:" msgstr "" #: ../../content/administration/install/packages.rst:148 #: ../../content/administration/install/source.rst:70 #: ../../content/administration/install/source.rst:129 #: ../../content/administration/install/source.rst:154 #: ../../content/administration/install/source.rst:176 #: ../../content/administration/install/source.rst:204 #: ../../content/administration/install/source.rst:235 #: ../../content/administration/install/source.rst:320 #: ../../content/administration/install/source.rst:389 #: ../../content/administration/install/source.rst:452 msgid "Windows" msgstr "" #: ../../content/administration/install/packages.rst:151 msgid "" "Windows packaging is offered for the convenience of testing or running " "single-user local instances but production deployment is discouraged due to " "a number of limitations and risks associated with deploying Odoo on a " "Windows platform." msgstr "" #: ../../content/administration/install/packages.rst:155 msgid "" "Download the installer from the `nightly server `_" " (Community only) or the Windows installer from the `Odoo download page " "`_ (any edition." msgstr "" #: ../../content/administration/install/packages.rst:158 msgid "Execute the downloaded file." msgstr "" #: ../../content/administration/install/packages.rst:161 msgid "" "On Windows 8 and later, a warning titled *Windows protected your PC* may be " "displayed. Click **More Info** and then **Run anyway** to proceed." msgstr "" #: ../../content/administration/install/packages.rst:164 msgid "" "Accept the `UAC `_ " "prompt." msgstr "" #: ../../content/administration/install/packages.rst:165 msgid "Go through the installation steps." msgstr "" #: ../../content/administration/install/packages.rst:167 msgid "Odoo launches automatically at the end of the installation." msgstr "" #: ../../content/administration/install/source.rst:3 msgid "Source" msgstr "지원 경로" #: ../../content/administration/install/source.rst:5 msgid "" "The source 'installation' is not about installing Odoo but running it " "directly from the source instead." msgstr "" #: ../../content/administration/install/source.rst:8 msgid "" "Using the Odoo source can be more convenient for module developers as it is " "more easily accessible than using packaged installers." msgstr "" #: ../../content/administration/install/source.rst:11 msgid "" "It makes starting and stopping Odoo more flexible and explicit than the " "services set up by the packaged installers. Also, it allows overriding " "settings using :ref:`command-line parameters ` without " "needing to edit a configuration file." msgstr "" #: ../../content/administration/install/source.rst:15 msgid "" "Finally, it provides greater control over the system's setup and allows to " "more easily keep (and run) multiple versions of Odoo side-by-side." msgstr "" #: ../../content/administration/install/source.rst:19 msgid "Fetch the sources" msgstr "" #: ../../content/administration/install/source.rst:21 msgid "" "There are two ways to obtain the source code of Odoo: as a ZIP **archive** " "or through **Git**." msgstr "" #: ../../content/administration/install/source.rst:24 msgid "Archive" msgstr "보관" #: ../../content/administration/install/source.rst:26 msgid "Community edition:" msgstr "" #: ../../content/administration/install/source.rst:28 #: ../../content/administration/install/source.rst:34 msgid "`Odoo download page `_" msgstr "" #: ../../content/administration/install/source.rst:29 msgid "`GitHub Community repository `_" msgstr "" #: ../../content/administration/install/source.rst:30 msgid "`Nightly server `_" msgstr "" #: ../../content/administration/install/source.rst:32 msgid "Enterprise edition:" msgstr "" #: ../../content/administration/install/source.rst:35 msgid "`GitHub Enterprise repository `_" msgstr "" #: ../../content/administration/install/source.rst:40 msgid "Git" msgstr "" #: ../../content/administration/install/source.rst:43 msgid "" "It is required to have `Git `_ installed, and it is " "recommended to have a basic knowledge of Git commands to proceed." msgstr "" #: ../../content/administration/install/source.rst:46 msgid "" "To clone a Git repository, choose between cloning with HTTPS or SSH. In most" " cases, the best option is HTTPS. However, choose SSH to contribute to Odoo " "source code or when following the :doc:`Getting Started developer tutorial " "`." msgstr "" #: ../../content/administration/install/source.rst:56 #: ../../content/administration/install/source.rst:74 #: ../../content/administration/install/source.rst:92 msgid "Clone with HTTPS" msgstr "" #: ../../content/administration/install/source.rst:63 #: ../../content/administration/install/source.rst:81 #: ../../content/administration/install/source.rst:99 msgid "Clone with SSH" msgstr "" #: ../../content/administration/install/source.rst:88 #: ../../content/administration/install/source.rst:137 #: ../../content/administration/install/source.rst:160 #: ../../content/administration/install/source.rst:182 #: ../../content/administration/install/source.rst:209 #: ../../content/administration/install/source.rst:249 #: ../../content/administration/install/source.rst:343 #: ../../content/administration/install/source.rst:401 #: ../../content/administration/install/source.rst:463 msgid "Mac OS" msgstr "" #: ../../content/administration/install/source.rst:107 msgid "" "**The Enterprise git repository does not contain the full Odoo source " "code**. It is only a collection of extra add-ons. The main server code is in" " the Community edition. Running the Enterprise version means running the " "server from the Community version with the `addons-path` option set to the " "folder with the Enterprise edition. It is required to clone both the " "Community and Enterprise repositories to have a working Odoo Enterprise " "installation." msgstr "" "**엔터프라이즈 git 저장소에는 전체 Odoo 소스 코드가 포함되어 있지 않습니다**. 이는 추가 애드온을 모아놓은 것에 불과합니다. " "메인 서버 코드는 커뮤니티 버전에 있습니다. 엔터프라이즈 버전을 실행한다는 것은, 커뮤니티 버전에서 서버를 실행하고 `addons-" "path` 옵션을 엔터프라이즈 버전이 있는 폴더로 설정하는 것을 의미합니다. Odoo 엔터프라이즈 설치를 제대로 동작하도록 실행하기 " "위해서는 커뮤니티 및 엔터프라이즈 저장소를 모두 복제해야 합니다." #: ../../content/administration/install/source.rst:119 msgid "Python" msgstr "파이선" #: ../../content/administration/install/source.rst:121 msgid "Odoo requires **Python 3.7** or later to run." msgstr "" #: ../../content/administration/install/source.rst:127 msgid "Use a package manager to download and install Python 3 if needed." msgstr "" #: ../../content/administration/install/source.rst:131 msgid "" "`Download the latest version of Python 3 " "`_ and install it." msgstr "" #: ../../content/administration/install/source.rst:134 msgid "" "During installation, check **Add Python 3 to PATH**, then click **Customize " "Installation** and make sure that **pip** is checked." msgstr "" #: ../../content/administration/install/source.rst:139 msgid "" "Use a package manager (`Homebrew `_, `MacPorts " "`_) to download and install Python 3 if needed." msgstr "" #: ../../content/administration/install/source.rst:143 msgid "" "If Python 3 is already installed, make sure that the version is 3.7 or " "above, as previous versions are not compatible with Odoo." msgstr "" #: ../../content/administration/install/source.rst:166 msgid "" "Verify that `pip `_ is also installed for this version." msgstr "" #: ../../content/administration/install/source.rst:191 msgid "Odoo uses PostgreSQL as its database management system." msgstr "" #: ../../content/administration/install/source.rst:197 msgid "" "Use a package manager to download and install PostgreSQL (supported " "versions: 12.0 or above). It can be achieved by executing the following:" msgstr "" #: ../../content/administration/install/source.rst:206 msgid "" "`Download PostgreSQL `_ " "(supported versions: 12.0 or above) and install it." msgstr "" #: ../../content/administration/install/source.rst:211 msgid "" "Use `Postgres.app `_ to download and install " "PostgreSQL (supported version: 12.0 or above)." msgstr "" #: ../../content/administration/install/source.rst:215 msgid "" "To make the command line tools bundled with Postgres.app available, make " "sure to set up the `$PATH` variable by following the `Postgres.app CLI tools" " instructions `_." msgstr "" #: ../../content/administration/install/source.rst:219 msgid "" "By default, the only user is `postgres`. As Odoo forbids connecting as " "`postgres`, create a new PostgreSQL user." msgstr "" #: ../../content/administration/install/source.rst:232 #: ../../content/administration/install/source.rst:257 msgid "" "Because the PostgreSQL user has the same name as the Unix login, it is " "possible to connect to the database without a password." msgstr "" #: ../../content/administration/install/source.rst:237 msgid "" "Add PostgreSQL's `bin` directory (by default: :file:`C:\\\\Program " "Files\\\\PostgreSQL\\\\\\\\bin`) to the `PATH`." msgstr "" #: ../../content/administration/install/source.rst:239 msgid "Create a postgres user with a password using the pg admin gui:" msgstr "" #: ../../content/administration/install/source.rst:241 msgid "Open **pgAdmin**." msgstr "" #: ../../content/administration/install/source.rst:242 msgid "Double-click the server to create a connection." msgstr "" #: ../../content/administration/install/source.rst:243 msgid "Select :menuselection:`Object --> Create --> Login/Group Role`." msgstr "" #: ../../content/administration/install/source.rst:244 msgid "Enter the username in the **Role Name** field (e.g., `odoo`)." msgstr "" #: ../../content/administration/install/source.rst:245 msgid "" "Open the **Definition** tab, enter a password (e.g., `odoo`), and click " "**Save**." msgstr "" #: ../../content/administration/install/source.rst:246 msgid "" "Open the **Privileges** tab and switch **Can login?** to `Yes` and **Create " "database?** to `Yes`." msgstr "" #: ../../content/administration/install/source.rst:263 msgid "Dependencies" msgstr "의존성" #: ../../content/administration/install/source.rst:269 msgid "" "Using **distribution packages** is the preferred way of installing " "dependencies. Alternatively, install the Python dependencies with **pip**." msgstr "" #: ../../content/administration/install/source.rst:276 msgid "" "For Debian-based systems, the packages are listed in the `debian/control " "`_ file of the Odoo " "sources." msgstr "" #: ../../content/administration/install/source.rst:279 msgid "" "On Debian/Ubuntu, the following commands should install the required " "packages:" msgstr "" #: ../../content/administration/install/source.rst:286 msgid "Install with pip" msgstr "" #: ../../content/administration/install/source.rst:288 msgid "" "As some of the Python packages need a compilation step, they require system " "libraries to be installed." msgstr "" #: ../../content/administration/install/source.rst:291 msgid "" "On Debian/Ubuntu, the following command should install these required " "libraries:" msgstr "" #: ../../content/administration/install/source.rst:297 msgid "" "Odoo dependencies are listed in the :file:`requirements.txt` file located at" " the root of the Odoo Community directory." msgstr "" #: ../../content/administration/install/source.rst:301 msgid "" "The Python packages in :file:`requirements.txt` are based on their " "stable/LTS Debian/Ubuntu corresponding version at the moment of the Odoo " "release. For example, for Odoo 15.0, the `python3-babel` package version is " "2.8.0 in Debian Bullseye and 2.6.0 in Ubuntu Focal. The lowest version is " "then chosen in the :file:`requirements.txt`." msgstr "" #: ../../content/administration/install/source.rst:308 #: ../../content/administration/install/source.rst:330 #: ../../content/administration/install/source.rst:349 msgid "" "It can be preferable not to mix Python module packages between different " "instances of Odoo or with the system. However, it is possible to use " "`virtualenv `_ to create isolated " "Python environments." msgstr "" #: ../../content/administration/install/source.rst:312 msgid "" "Navigate to the path of the Odoo Community installation " "(:file:`CommunityPath`) and run **pip** on the requirements file to install " "the requirements for the current user." msgstr "" #: ../../content/administration/install/source.rst:322 msgid "" "Before installing the dependencies, download and install the `Build Tools " "for Visual Studio `_. Select " "**C++ build tools** in the **Workloads** tab and install them when prompted." msgstr "" #: ../../content/administration/install/source.rst:326 #: ../../content/administration/install/source.rst:345 msgid "" "Odoo dependencies are listed in the `requirements.txt` file located at the " "root of the Odoo Community directory." msgstr "" #: ../../content/administration/install/source.rst:334 msgid "" "Navigate to the path of the Odoo Community installation (`CommunityPath`) " "and run **pip** on the requirements file in a terminal **with Administrator " "privileges**:" msgstr "" #: ../../content/administration/install/source.rst:353 msgid "" "Navigate to the path of the Odoo Community installation (`CommunityPath`) " "and run **pip** on the requirements file:" msgstr "" #: ../../content/administration/install/source.rst:363 msgid "" "Non-Python dependencies must be installed with a package manager (`Homebrew " "`_, `MacPorts `_)." msgstr "" #: ../../content/administration/install/source.rst:366 msgid "Download and install the **Command Line Tools**:" msgstr "" #: ../../content/administration/install/source.rst:372 msgid "Use the package manager to install non-Python dependencies." msgstr "" #: ../../content/administration/install/source.rst:375 msgid "" "For languages using a **right-to-left interface** (such as Arabic or " "Hebrew), the `rtlcss` package is required." msgstr "" #: ../../content/administration/install/source.rst:382 msgid "Download and install **nodejs** and **npm** with a package manager." msgstr "" #: ../../content/administration/install/source.rst:383 #: ../../content/administration/install/source.rst:392 #: ../../content/administration/install/source.rst:405 msgid "Install `rtlcss`:" msgstr "" #: ../../content/administration/install/source.rst:391 msgid "Download and install `nodejs `_." msgstr "" #: ../../content/administration/install/source.rst:398 msgid "" "Edit the system environment's variable `PATH` to add the folder where " "`rtlcss.cmd` is located (typically: " ":file:`C:\\\\Users\\\\\\\\AppData\\\\Roaming\\\\npm\\\\`)." msgstr "" #: ../../content/administration/install/source.rst:403 msgid "" "Download and install **nodejs** with a package manager (`Homebrew " "`_, `MacPorts `_)." msgstr "" #: ../../content/administration/install/source.rst:420 msgid "Running Odoo" msgstr "" #: ../../content/administration/install/source.rst:422 msgid "" "Once all dependencies are set up, Odoo can be launched by running `odoo-" "bin`, the command-line interface of the server. It is located at the root of" " the Odoo Community directory." msgstr "" #: ../../content/administration/install/source.rst:425 msgid "" "To configure the server, either specify :ref:`command-line arguments " "` or a :ref:`configuration file " "`." msgstr "" #: ../../content/administration/install/source.rst:429 msgid "" "For the Enterprise edition, add the path to the `enterprise` add-ons to the " "`addons-path` argument. Note that it must come before the other paths in " "`addons-path` for add-ons to be loaded correctly." msgstr "" #: ../../content/administration/install/source.rst:433 msgid "Common necessary configurations are:" msgstr "" #: ../../content/administration/install/source.rst:435 msgid "PostgreSQL user and password." msgstr "" #: ../../content/administration/install/source.rst:436 msgid "Custom addon paths beyond the defaults to load custom modules." msgstr "" #: ../../content/administration/install/source.rst:438 msgid "A typical way to run the server would be:" msgstr "" #: ../../content/administration/install/source.rst:449 #: ../../content/administration/install/source.rst:470 msgid "" "Where `CommunityPath` is the path of the Odoo Community installation, and " "`mydb` is the name of the PostgreSQL database." msgstr "" #: ../../content/administration/install/source.rst:459 msgid "" "Where `CommunityPath` is the path of the Odoo Community installation, " "`dbuser` is the PostgreSQL login, `dbpassword` is the PostgreSQL password, " "and `mydb` is the name of the PostgreSQL database." msgstr "" #: ../../content/administration/install/source.rst:473 msgid "" "After the server has started (the INFO log `odoo.modules.loading: Modules " "loaded.` is printed), open http://localhost:8069 in a web browser and log " "into the Odoo database with the base administrator account: use `admin` as " "the email and, again, `admin` as the password." msgstr "" #: ../../content/administration/install/source.rst:478 msgid "" "From there, create and manage new :doc:`users " "<../../applications/general/users/manage_users>`." msgstr "" #: ../../content/administration/install/source.rst:479 msgid "" "The user account used to log into Odoo's web interface differs from the " ":option:`--db_user ` CLI argument." msgstr "" #: ../../content/administration/install/source.rst:483 msgid "" ":doc:`The list of CLI arguments for odoo-bin `" msgstr "" #: ../../content/administration/maintain.rst:5 msgid "Maintain" msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:3 msgid "Connect Microsoft Outlook 365 to Odoo using Azure OAuth" msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:5 msgid "" "Odoo is compatible with Microsoft's Azure OAuth for Microsoft 365. In order " "to send and receive secure emails from a custom domain, all that is required" " is to configure a few settings on the Azure platform and on the back end of" " the Odoo database. This configuration works with either a personal email " "address or an address created by a custom domain." msgstr "" "Odoo는 Microsoft의 Microsoft 365용 Azure OAuth와 호환됩니다. 사용자 지정 도메인에서 보안 이메일을 " "송수신하려면 Azure 플랫폼과 Odoo 데이터베이스의 백엔드에서 몇 가지 설정만 구성하면 됩니다. 해당 설정 내용은 개인 이메일 주소 " "또는 사용자 지정 도메인에서 만든 주소 모두에서 작동합니다." #: ../../content/administration/maintain/azure_oauth.rst:11 msgid "" "`Microsoft Learn: Register an application with the Microsoft identity " "platform `_" msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:15 msgid ":doc:`/applications/general/auth/azure`" msgstr ":doc:`/applications/general/auth/azure`" #: ../../content/administration/maintain/azure_oauth.rst:16 msgid ":doc:`/applications/productivity/calendar/outlook`" msgstr ":doc:`/applications/productivity/calendar/outlook`" #: ../../content/administration/maintain/azure_oauth.rst:19 msgid "Setup in Microsoft Azure Portal" msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:22 msgid "Create a new application" msgstr "새로운 애플리케이션 생성하기" #: ../../content/administration/maintain/azure_oauth.rst:24 msgid "" "To get started, go to `Microsoft's Azure Portal " "`_. Log in with the :guilabel:`Microsoft Outlook " "Office 365` account if there is one, otherwise log in with the personal " ":guilabel:`Microsoft account`. A user with administrative access to the " "Azure Settings will need to connect and perform the following configuration." " Next, navigate to the section labeled :guilabel:`Manage Microsoft Entra ID`" " (formally *Azure Active Directory*)." msgstr "" "시작하려면 `Microsoft's Azure Portal `_로 이동하세요. " ":guilabel:`Microsoft Outlook Office 365` 계정이 있는 경우에는 해당 계정으로 로그인하고, 그렇지 않은 " "경우 개인 :guilabel:`Microsoft 계정`으로 로그인합니다. Azure 설정에 대한 관리 액세스 권한이 있는 사용자는 접속 " "후 다음과 같이 설정해야 합니다. 그런 다음 :guilabel:`Microsoft Entra ID 관리` (공식적으로는 *Azure " "액티브 디렉토리*) 섹션으로 이동합니다." #: ../../content/administration/maintain/azure_oauth.rst:30 msgid "" "Now, click on :guilabel:`Add (+)`, located in the top menu, and then select " ":guilabel:`App registration`. On the :guilabel:`Register an application` " "screen, rename the :guilabel:`Name` to `Odoo` or something recognizable. " "Under the :guilabel:`Supported account types` section select " ":guilabel:`Accounts in any organizational directory (Any Microsoft Entra ID " "directory - Multitenant) and personal Microsoft accounts (e.g. Skype, " "Xbox)`." msgstr "" "이제 상단 메뉴에 있는 :guilabel:`추가 (+)`를 클릭한 다음 :guilabel:`앱 등록`을 선택하세요. '애플리케이션 등록'" " 화면에서 '이름'을 'Odoo' 또는 확인할 수 있는 이름으로 변경합니다. :guilabel:`지원되는 계정 유형` 섹션에서 " ":guilabel:`전체 조직 디렉토리 계정 (전체 Microsoft Entra ID 디렉토리 - 멀티 테넌트) 및 Microsoft " "개인 계정 (e.g. Skype, Xbox)`을 선택합니다." #: ../../content/administration/maintain/azure_oauth.rst:36 msgid "" "Under the :guilabel:`Redirect URL` section, select :guilabel:`Web` as the " "platform, and then input `https:///microsoft_outlook/confirm`" " in the :guilabel:`URL` field. The Odoo base URL is the canonical domain at " "which your Odoo instance can be reached in the URL field." msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:41 msgid "" "*mydatabase.odoo.com*, where *mydatabase* is the actual prefix of the " "database's subdomain, assuming it's hosted on Odoo.com" msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:44 msgid "" "After the URL has been added to the field, :guilabel:`Register` the " "application so it is created." msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:47 msgid "API permissions" msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:49 msgid "" "The :guilabel:`API permissions` should be set next. Odoo will need specific " "API permissions to be able to read (IMAP) and send (SMTP) emails in the " "Microsoft 365 setup. First, click the :guilabel:`API permissions` link, " "located in the left menu bar. Next, click on the :guilabel:`(+) Add a " "Permission` button and select :guilabel:`Microsoft Graph` under " ":guilabel:`Commonly Used Microsoft APIs`. After, select the " ":guilabel:`Delegated Permissions` option." msgstr "" "다음으로 :guilabel:`API 권한`을 설정해야 합니다. Odoo에서 Microsoft 365 설정 하의 이메일을 읽고 (IMAP)" " 보낼 (SMTP) 수 있으려면 특정 API 권한이 필요합니다. 먼저 왼쪽 메뉴 표시줄에 있는 :guilabel:`API 권한` 링크를 " "클릭합니다. 다음으로, :guilabel:` (+) 권한 추가` 버튼을 클릭하고 :guilabel:`일반적으로 사용되는 Microsoft" " API` 아래에서 :guilabel:`Microsoft 그래프`를 선택합니다. 그 후, :guilabel:`위임된 권한` 옵션을 " "선택합니다." #: ../../content/administration/maintain/azure_oauth.rst:55 msgid "" "In the search bar, search for the following :guilabel:`Deregulated " "permissions` and click :guilabel:`Add permissions` for each one:" msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:58 msgid ":guilabel:`SMTP.Send`" msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:59 msgid ":guilabel:`IMAP.AccessAsUser.All`" msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:62 msgid "The :guilabel:`User.Read` permission will be added by default." msgstr "" #: ../../content/administration/maintain/azure_oauth.rst-1 msgid "" "API permissions needed for Odoo integration are listed under the Microsoft " "Graph." msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:69 msgid "Assign users and groups" msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:71 msgid "" "After adding the API permissions, navigate back to the :guilabel:`Overview` " "of the :guilabel:`Application` in the top of the left sidebar menu." msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:74 msgid "" "Now, add users to this application. Under the :guilabel:`Essentials` " "overview table, click on the link labeled :guilabel:`Managed Application in " "Local Directory`, or the last option on the bottom right-hand side of the " "table." msgstr "" #: ../../content/administration/maintain/azure_oauth.rst-1 msgid "" "Add users/groups by clicking the Managed application in local directory link for the\n" "created application." msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:83 msgid "" "In the left sidebar menu, select :guilabel:`Users and Groups`. Next, click " "on :guilabel:`(+) Add User/Group`. Depending on the account, either a " ":guilabel:`Group` and a :guilabel:`User` can be added, or only " ":guilabel:`Users`. Personal accounts will only allow for :guilabel:`Users` " "to be added." msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:88 msgid "" "Under :guilabel:`Users` or :guilabel:`Groups`, click on :guilabel:`None " "Selected` and add the users or group of users that will be sending emails " "from the :guilabel:`Microsoft account` in Odoo. :guilabel:`Add` the " "users/groups, click :guilabel:`Select`, and then :guilabel:`Assign` them to " "the application." msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:94 msgid "Create credentials" msgstr "자격증명 생성" #: ../../content/administration/maintain/azure_oauth.rst:96 msgid "" "Now that the Microsoft Azure app is set up, credentials need to be created " "for the Odoo setup. These include the :guilabel:`Client ID` and " ":guilabel:`Client Secret`. To start, the :guilabel:`Client ID` can be copied" " from the :guilabel:`Overview` page of the app. The :guilabel:`Client ID` or" " :guilabel:`Application ID` is located under the :guilabel:`Display Name` in" " the :guilabel:`Essentials` overview of the app." msgstr "" "이제 Microsoft Azure 앱이 설정되었으므로 Odoo 설정을 위한 자격 증명을 생성해야 합니다. 여기에는 " ":guilabel:`클라이언트 ID` 및 :guilabel:`클라이언트 비밀번호`가 포함됩니다. 시작하려면 앱에 있는 " ":guilabel:`클라이언트 ID`를 :guilabel:`전체 보기` 페이지에서 복사할 수 있습니다. :guilabel:`클라이언트 " "ID` 또는 :guilabel:`애플리케이션 ID`는 앱의 :guilabel:`주요 내용` 전체 보기에 있는 :guilabel:`표시 " "이름` 아래에 있습니다." #: ../../content/administration/maintain/azure_oauth.rst-1 msgid "Application/Client ID located in the Overview of the app." msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:106 msgid "" "Next, the :guilabel:`Client Secret Value` needs to be retrieved. To get this" " value, click on :guilabel:`Certificates & Secrets` in the left sidebar " "menu. Then, a :guilabel:`Client Secret` needs to be produced. In order to do" " this, click on the :guilabel:`(+) New Client Secret` button." msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:110 msgid "" "A window on the right will populate with a button labeled :guilabel:`Add a " "client secret`. Under :guilabel:`Description`, type in `Odoo Fetchmail` or " "something recognizable, and then set the :guilabel:`expiration date`." msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:115 msgid "" "A new :guilabel:`Client Secret` will need to be produced and configured if " "the first one expires. In this event, there could be an interruption of " "service, so the expiration date should be noted and set to the furthest " "possible date." msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:119 msgid "" "Next, click on :guilabel:`Add` when these two values are entered. A " ":guilabel:`Client Secret Value` and :guilabel:`Secret ID` will be created. " "It is important to copy the :guilabel:`Value` or :guilabel:`Client Secret " "Value` into a notepad as it will become encrypted after leaving this page. " "The :guilabel:`Secret ID` is not needed." msgstr "" #: ../../content/administration/maintain/azure_oauth.rst-1 msgid "Client Secret Value or Value in the app's credentials." msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:128 msgid "" "After these steps, the following items should be ready to be set up in Odoo:" msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:130 msgid "A client ID (:guilabel:`Client ID` or :guilabel:`Application ID`)" msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:131 msgid "A client secret (:guilabel:`Value` or :guilabel:`Client Secret Value`)" msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:133 msgid "" "This completes the setup on the :guilabel:`Microsoft Azure Portal` side." msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:136 #: ../../content/administration/maintain/google_oauth.rst:111 msgid "Setup in Odoo" msgstr "Odoo에서 설정" #: ../../content/administration/maintain/azure_oauth.rst:139 msgid "Enter Microsoft Outlook credentials" msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:141 msgid "" "First, open the Odoo database and navigate to the :guilabel:`Apps` module. " "Then, remove the :guilabel:`Apps` filter from the search bar and type in " "`Outlook`. After that, install the module called :guilabel:`Microsoft " "Outlook`." msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:145 msgid "" "Next, navigate to :menuselection:`Settings --> General Settings`, and under " "the :guilabel:`Discuss` section, ensure that the checkbox for " ":guilabel:`Custom Email Servers` is checked. This populates a new option for" " :guilabel:`Outlook Credentials`." msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:149 msgid ":guilabel:`Save` the progress." msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:151 msgid "" "Then, copy and paste the :guilabel:`Client ID` (Application ID) and " ":guilabel:`Client Secret (Client Secret Value)` into the respective fields " "and :guilabel:`Save` the settings." msgstr "" #: ../../content/administration/maintain/azure_oauth.rst-1 msgid "Outlook Credentials in Odoo General Settings." msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:159 #: ../../content/administration/maintain/google_oauth.rst:127 msgid "Configure outgoing email server" msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:161 msgid "" "On the :guilabel:`General Settings` page, under the :guilabel:`Custom Email " "Servers` setting, click the :guilabel:`Outgoing Email Servers` link to " "configure the Microsoft account." msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:164 msgid "" "Then, create a new email server and check the box for :guilabel:`Outlook`. " "Next, fill in the :guilabel:`Name` (it can be anything) and the Microsoft " "Outlook email :guilabel:`Username`." msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:167 msgid "" "If the :guilabel:`From Filter` field is empty, enter either a :ref:`domain " "or email address `." msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:170 msgid "Then, click on :guilabel:`Connect your Outlook account`." msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:172 msgid "" "A new window from Microsoft opens to complete the :guilabel:`authorization " "process`. Select the appropriate email address that is being configured in " "Odoo." msgstr "" #: ../../content/administration/maintain/azure_oauth.rst-1 msgid "Permission page to grant access between newly created app and Odoo." msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:179 msgid "" "Then, allow Odoo to access the Microsoft account by clicking on " ":guilabel:`Yes`. After this, the page will navigate back to the newly " "configured :guilabel:`Outgoing Mail Server` in Odoo. The configuration " "automatically loads the :guilabel:`token` in Odoo, and a tag stating " ":guilabel:`Outlook Token Valid` appears in green." msgstr "" #: ../../content/administration/maintain/azure_oauth.rst-1 msgid "Valid Outlook Token indicator." msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:188 msgid "" "Finally, click :guilabel:`Test Connection`. A confirmation message should " "appear. The Odoo database can now send safe, secure emails through Microsoft" " Outlook using OAuth authentication." msgstr "" "마지막으로, :guilabel:`테스트 연결`을 클릭합니다. 확인 메시지가 나타날 것입니다. Odoo 데이터베이스에서 이제 OAuth " "인증을 사용하여 Microsoft Outlook을 통해 안전하게 보안 이메일을 발송할 수 있습니다. " #: ../../content/administration/maintain/azure_oauth.rst:194 msgid "Configuration with a single outgoing mail server" msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:196 msgid "" "Configuring a single outgoing server is the simplest configuration available" " for Microsoft Azure and it doesn't require extensive access rights for the " "users in the database." msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:199 msgid "" "A generic email address would be used to send emails for all users within " "the database. For example it could be structured with a `notifications` " "alias (`notifications@example.com`) or `contact` alias " "(`contact@example.com`). This address must be set as the :guilabel:`FROM " "Filtering` on the server. This address must also match the " "`{mail.default.from}@{mail.catchall.domain}` key combination in the system " "parameters." msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:206 #: ../../content/administration/maintain/azure_oauth.rst:247 msgid "" "For more information on the from filter visit: " ":ref:`email_communication/default`." msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:209 #: ../../content/administration/maintain/azure_oauth.rst:254 msgid "" "The :guilabel:`System Parameters` can be accessed by activating " ":ref:`developer-mode` in the :menuselection:`Settings --> Technical --> " "Parameters --> System Parameters` menu." msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:212 msgid "" "When using this configuration, every email that is sent from the database " "will use the address of the configured `notification` mailbox. However it " "should be noted that the name of the sender will appear but their email " "address will change:" msgstr "" #: ../../content/administration/maintain/azure_oauth.rst-1 msgid "Name from real sender with static email." msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:221 msgid "Single outgoing mail server configuration:" msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:223 msgid "" "Outgoing mail server **username** (login) = `notifications@example.com`" msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:224 msgid "" "Outgoing mail server :guilabel:`FROM Filtering` = " "`notifications@example.com`" msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:225 #: ../../content/administration/maintain/azure_oauth.rst:279 msgid "`mail.catchall.domain` in system parameters = `example.com`" msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:226 #: ../../content/administration/maintain/azure_oauth.rst:280 msgid "`mail.default.from` in system parameters = `notifications`" msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:229 msgid "User-specific (multiple user) configuration" msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:231 msgid "" "In addition to a generic email server, individual email servers can be set " "up for users in a database. These email addresses must be set as the " ":guilabel:`FROM Filtering` on each individual server for this configuration " "to work." msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:235 msgid "" "This configuration is the more difficult of the two Microsoft Azure " "configurations, in that it requires all users configured with email servers " "to have access rights to settings in order to establish a connection to the " "email server." msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:240 #: ../../content/administration/odoo_sh/getting_started/branches.rst:480 msgid "Setup" msgstr "설정" #: ../../content/administration/maintain/azure_oauth.rst:242 msgid "" "Each user should have a separate email server set up. The :guilabel:`FROM " "Filtering` should be set so that only the user's email is sent from that " "server. In other words, only a user with an email address that matches the " "set :guilabel:`FROM Filtering` is able to use this server." msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:249 msgid "" "A :ref:`fallback server ` must be setup to allow " "for the sending of :guilabel:`notifications`. The :guilabel:`FROM Filtering`" " for this server should have the value of the " "`{mail.default.from}@{mail.catchall.domain}`." msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:258 msgid "" "The configuration for this transactional email server can work alongside an " "outgoing mass-mailing email server. The :guilabel:`FROM Filtering` for the " "mass-mailing email server can remain empty, but it's require to be added in " "the settings of the *Email Marketing* application." msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:263 msgid "" "For more information on setting the mass-mailing email server visit " ":ref:`email_communication/mass_mails`." msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:267 msgid "Multiple user outgoing mail server configuration:" msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:270 msgid "User #1 mailbox" msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:270 msgid "Outgoing mail server #1 **username** (login) = `john@example.com`" msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:271 msgid "" "Outgoing mail server #1 :guilabel:`FROM Filtering` = `john@example.com`" msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:273 msgid "User #2 mailbox" msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:273 msgid "Outgoing mail server #2 **username** (login) = `jane@example.com`" msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:274 msgid "" "Outgoing mail server #2 :guilabel:`FROM Filtering` = `jane@example.com`" msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:276 msgid "Notifications mailbox" msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:276 msgid "" "Outgoing mail server #3 **username** (login) = `notifications@example.com`" msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:277 msgid "" "Outgoing mail server #3 :guilabel:`FROM Filtering` = " "`notifications@example.com`" msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:279 msgid "System Parameters" msgstr "시스템 매개 변수" #: ../../content/administration/maintain/azure_oauth.rst:283 msgid "Configure incoming email server" msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:285 msgid "" "The incoming account should be configured in a similar way to the outgoing " "email account. Navigate to the :guilabel:`Incoming Mail Servers` in the " ":guilabel:`Technical Menu` and :guilabel:`Create` a new configuration. Check" " or Select the button next to :guilabel:`Outlook Oauth Authentication` and " "enter the :guilabel:`Microsoft Outlook username`. Click on " ":guilabel:`Connect your Outlook account`. Odoo will state: " ":guilabel:`Outlook Token Valid` Now :guilabel:`Test and Confirm` the " "account. The account should be ready to receive email to the Odoo database." msgstr "" "수신 계정은 이메일 발신 계정과 유사한 방식으로 구성되어야 합니다. :guilabel:`기술 메뉴`내의 :guilabel:`수신 메일 " "서버`로 이동하여 :guilabel:`생성`으로 새로 구성을 진행하십시오. :guilabel:`Outlook Oauth 인증` 옆에 있는" " 버튼을 확인하거나 선택한 후 :guilabel:`Microsoft Outlook 사용자 이름`을 입력합니다. " ":guilabel:`Outlook 계정에 연결`을 클릭합니다. Odoo에서 :guilabel:`Outlook 토큰 유효함` 메시지를 " "확인하실 수 있습니다. 이제 계정에 :guilabel:`테스트 및 확인`을 진행합니다. 계정에서 Odoo 데이터베이스로 이메일을 수신할 " "준비가 되어 있어야 합니다." #: ../../content/administration/maintain/azure_oauth.rst:293 msgid ":doc:`../../applications/general/email_communication/email_servers`" msgstr "" #: ../../content/administration/maintain/domain_names.rst:3 #: ../../content/administration/maintain/odoo_online.rst:70 msgid "Domain names" msgstr "" #: ../../content/administration/maintain/domain_names.rst:5 msgid "" "A **domain name** works as an address for your website. It makes the " "Internet much more accessible as it allows users to type a meaningful web " "address, such as ``www.odoo.com``, rather than its server's IP address with " "a series of numbers." msgstr "" #: ../../content/administration/maintain/domain_names.rst:9 msgid "" "You can use a custom domain name to access your Odoo database and websites:" msgstr "" #: ../../content/administration/maintain/domain_names.rst:11 msgid "" "By :ref:`registering a free domain name with Odoo ` (for Odoo Online databases)" msgstr "" #: ../../content/administration/maintain/domain_names.rst:13 msgid "" "By :ref:`configuring a custom domain that you already own `." msgstr "" #: ../../content/administration/maintain/domain_names.rst:16 msgid "" "Odoo Online and Odoo.sh databases, including their websites, use by default " "a subdomain of ``odoo.com`` for both the URL and the emails (e.g., " "``https://example.odoo.com``)." msgstr "" #: ../../content/administration/maintain/domain_names.rst:20 msgid "" "Odoo offers a :ref:`free custom domain name ` to " "all Odoo Online databases for one year. Visitors can then access your " "website with an address such as ``www.example.com`` rather than the default " "``example.odoo.com``." msgstr "" "Odoo는 모든 온라인 데이터베이스에 1년 동안 :ref:`free 커스텀 도메인 네임 ` 을 제공합니다. 이를 통해 방문자는 기본 주소인 ``example.odoo.com`` 대신 " "``www.example.com``와 같은 주소로 웹사이트에 액세스할 수 있습니다." #: ../../content/administration/maintain/domain_names.rst:25 msgid "" "`Odoo Tutorials: Register a Free Domain Name " "`_" msgstr "" #: ../../content/administration/maintain/domain_names.rst:27 msgid "" "`Odoo Quick Tips: Get a free domain name! " "`_" msgstr "" #: ../../content/administration/maintain/domain_names.rst:32 msgid "About domain names" msgstr "" #: ../../content/administration/maintain/domain_names.rst:34 msgid "" "Having a **good domain name** is as important to your branding as the name " "of your business or organization as it is the first thing your visitors will" " notice. We recommend you keep them *simple, short, easy to remember and " "spell*." msgstr "" #: ../../content/administration/maintain/domain_names.rst:38 msgid "" "A **subdomain** is a domain that is a part of another domain. It often " "refers to the additional part that comes before the main domain name. " "Traditionally, most websites use the ``www.`` subdomain, but any string of " "letters can be used as well. You can use subdomains to direct your visitors " "to other websites than your main website or to specific pages (e.g., " "``experience.odoo.com`` points to a specific page.)" msgstr "" #: ../../content/administration/maintain/domain_names.rst:44 msgid "" "All domain names are referenced in the **Domain Name System**, or **DNS**, " "which works as a giant directory for the Internet. There are many DNS " "servers, so any modification to the DNS can take up to 72 hours to propagate" " worldwide on all servers." msgstr "" #: ../../content/administration/maintain/domain_names.rst:51 msgid "Indexing of domain names by search engines" msgstr "" #: ../../content/administration/maintain/domain_names.rst:53 msgid "" "Search engines, such as Google and Bing, rely on web crawlers (:dfn:`robots " "that explore and analyze the web`) to index all websites and their related " "domain names. These crawlers discover new URLs thanks to links on known web " "pages. As a result, search engines should index domain names automatically " "after a while, as long as their URLs are mentioned elsewhere on the " "Internet." msgstr "" "Google나 Bing과 같은 검색 엔진은 웹 크롤러 (:dfn:`웹을 탐색하고 분석하는 로봇`)를 사용하여 모든 웹사이트와 관련 도메인" " 이름을 인덱스로 만듭니다. 크롤러는 이미 알려진 웹 페이지의 링크를 통해 새로운 URL을 찾아냅니다. 따라서 검색 엔진은 도메인 이름이" " 인터넷의 다른 곳에서 참조 후 한 시간이 지나면 자동으로 인덱스를 생성해야 합니다." #: ../../content/administration/maintain/domain_names.rst:58 msgid "" "Improving the appearance and positioning of web pages on search engines is a" " practice named \"Search Engine Optimization\" (SEO)." msgstr "" #: ../../content/administration/maintain/domain_names.rst:62 msgid "" "Adding relevant content, optimizing metadata, and building high-quality " "backlinks can all help improve a website's search engine visibility." msgstr "" #: ../../content/administration/maintain/domain_names.rst:65 msgid "" "Some search engines provide tools for web admins, such as `Google Search " "Console `_ and `Bing Webmaster " "Tools `_, to help you analyze and improve " "your page ranking. To use these services, you must prove that you are the " "owner of your domain name. One way to verify the ownership of your domain " "name is by adding a DNS record. You can do this for :ref:`domain names " "registered with Odoo ` and for domain names managed" " by other providers." msgstr "" "일부 검색 엔진에서는 페이지 순위를 분석하고 개선할 수 있도록 웹 관리자를 위한 도구 (예: `Google Search Console " "`_ 및 `Bing 웹마스터 도구 " "`_)를 서비스하고 있습니다. 이러한 서비스를 이용하려면 해당 도메인 주소의 " "소유자임을 증명해야 합니다. 도메인 주소 소유권을 확인하는 방법 중 하나는 DNS 레코드를 추가하는 것입니다. :ref:`Odoo에 " "등록된 도메인 주소 `에서 등록한 도메인 주소 및 다른 공급업체에서 관리하는 도메인 주소에 " "대해 작업을 수행할 수 있습니다." #: ../../content/administration/maintain/domain_names.rst:74 msgid ":doc:`/applications/websites/website/pages/seo`" msgstr ":doc:`/applications/websites/website/pages/seo`" #: ../../content/administration/maintain/domain_names.rst:75 msgid "" "`Google Search Console Help - Verify your site ownership " "`_" msgstr "" #: ../../content/administration/maintain/domain_names.rst:76 msgid "" "`Bing Webmaster Tools - Add and Verify site " "`_" msgstr "" #: ../../content/administration/maintain/domain_names.rst:81 msgid "Register a free domain name with Odoo" msgstr "" #: ../../content/administration/maintain/domain_names.rst:83 msgid "" "You can register a domain name for your Odoo Online database directly from " "Odoo Website or your database manager." msgstr "" #: ../../content/administration/maintain/domain_names.rst:87 msgid "" "Your domain name is **free for one year** if you register it with Odoo!" msgstr "" #: ../../content/administration/maintain/domain_names.rst:88 msgid "" "The domain name is registered with `Gandi `_, the " "domain name registrar." msgstr "" #: ../../content/administration/maintain/domain_names.rst:90 msgid "" "You are the owner of the domain name and can use it for other purposes." msgstr "" #: ../../content/administration/maintain/domain_names.rst:91 msgid "Odoo manages payment and technical support for you." msgstr "" #: ../../content/administration/maintain/domain_names.rst:92 msgid "" "This offer doesn't include any mailbox. However, you can :ref:`configure " "your MX records ` to use your own email server or " "solution such as Google Workspace." msgstr "" #: ../../content/administration/maintain/domain_names.rst:95 msgid "" "To do so, go to :menuselection:`Website --> Domain Name`. Alternatively, " "open your `database manager `_, click on " "the :guilabel:`settings` button next to your database, then on " ":guilabel:`Domain names`." msgstr "" #: ../../content/administration/maintain/domain_names.rst-1 msgid "Clicking on Domain Names from an Odoo website" msgstr "" #: ../../content/administration/maintain/domain_names.rst:103 msgid "" "Search for the domain name of your choice to check its availability, then " "select the one you want to register for your website." msgstr "" #: ../../content/administration/maintain/domain_names.rst-1 msgid "" "The search of the domain name example.com shows which associated domains are" " available." msgstr "" #: ../../content/administration/maintain/domain_names.rst:110 msgid "" "Next, fill in the form with your information to become the domain name " "owner." msgstr "" #: ../../content/administration/maintain/domain_names.rst:112 msgid "" "Your domain name is directly linked to your database, but you still have to " ":ref:`map your domain name with your website `." msgstr "" #: ../../content/administration/maintain/domain_names.rst:116 msgid "" "Free domain names are also available for free Odoo Online databases (if you " "installed one app only, for example). In this case, Odoo reviews your " "request and your website to avoid abuse. This process can take several days " "due to the success of the offer." msgstr "" #: ../../content/administration/maintain/domain_names.rst:119 msgid "This is not available for Odoo.sh databases yet." msgstr "" #: ../../content/administration/maintain/domain_names.rst:124 msgid "Manage your domain name registered with Odoo" msgstr "" #: ../../content/administration/maintain/domain_names.rst:126 msgid "" "To manage the DNS records of your domain name registered with Odoo or to " "visualize the contacts associated with it, open your `database manager " "`_, click on the :guilabel:`settings` " "button next to your database, on :guilabel:`Domain names`, and then on " ":guilabel:`Contacts` or :guilabel:`DNS`." msgstr "" #: ../../content/administration/maintain/domain_names.rst-1 msgid "Management of the domain names linked to an Odoo database" msgstr "" #: ../../content/administration/maintain/domain_names.rst:136 msgid "" "Please `submit a support ticket `_ if you need " "further assistance to manage your domain name." msgstr "" #: ../../content/administration/maintain/domain_names.rst:142 msgid "Configure your existing domain name" msgstr "" #: ../../content/administration/maintain/domain_names.rst:144 msgid "" "If you already own a domain name, you can use it to point to your website." msgstr "" #: ../../content/administration/maintain/domain_names.rst:146 msgid "" "To avoid any issue with the :ref:`SSL certificate validation `, we highly recommend that you proceed with the following actions " "in this order:" msgstr "" #: ../../content/administration/maintain/domain_names.rst:149 msgid "" ":ref:`Add a CNAME record ` on your domain name's DNS " "zone." msgstr "" #: ../../content/administration/maintain/domain_names.rst:150 msgid "" ":ref:`Map your domain name with your Odoo database `." msgstr "" #: ../../content/administration/maintain/domain_names.rst:151 msgid "" ":ref:`Map your domain name with your Odoo website `." msgstr "" #: ../../content/administration/maintain/domain_names.rst:156 msgid "Add a CNAME record" msgstr "" #: ../../content/administration/maintain/domain_names.rst:158 msgid "" "A **CNAME record** is a type of DNS record that points to the domain of " "another website rather than directly to an IP address." msgstr "" #: ../../content/administration/maintain/domain_names.rst:161 msgid "" "You need a CNAME record that points to your Odoo database. The requirements " "are detailed in your database manager." msgstr "" #: ../../content/administration/maintain/domain_names.rst:168 msgid "" "The target address is the current address of your database, as defined at " "its creation (e.g., ``example.odoo.com``)" msgstr "" #: ../../content/administration/maintain/domain_names.rst:171 #: ../../content/administration/maintain/domain_names.rst:250 #: ../../content/administration/maintain/supported_versions.rst:30 #: ../../content/administration/odoo_sh.rst:5 #: ../../content/administration/upgrade.rst:120 #: ../../content/administration/upgrade.rst:318 msgid "Odoo.sh" msgstr "Odoo.sh" #: ../../content/administration/maintain/domain_names.rst:173 msgid "" "Your project's main address is defined in :menuselection:`Settings --> " "Project Name`." msgstr "" #: ../../content/administration/maintain/domain_names.rst:175 msgid "" "If you want to target a specific branch (production, staging or " "development), go to :menuselection:`Branches --> select your branch --> " "Settings --> Custom domains`, and click on :guilabel:`How to set up my " "domain?`. A message indicates which address your CNAME record should target." msgstr "" #: ../../content/administration/maintain/domain_names.rst:180 #: ../../content/administration/maintain/domain_names.rst:222 msgid "Open your domain name's manager dashboard." msgstr "" #: ../../content/administration/maintain/domain_names.rst:181 msgid "" "Open the **DNS zone** management page for the domain name you want to " "configure." msgstr "" #: ../../content/administration/maintain/domain_names.rst:182 msgid "Create a **CNAME record** pointing to the address of your database." msgstr "" #: ../../content/administration/maintain/domain_names.rst:184 msgid "" "While Odoo suggests creating a CNAME record for your ``www.`` subdomain " "(``www.example.com``), you can of course use any domain name of your choice," " with any subdomain (e.g., ``anything.example.com``)." msgstr "" #: ../../content/administration/maintain/domain_names.rst:189 msgid "" "You own the domain name ``example.com``, and you have an Odoo Online " "database at the address ``example.odoo.com``. You want to access your Odoo " "database primarily with the domain ``www.example.com`` but also with the " ":ref:`naked domain ` ``example.com``." msgstr "" #: ../../content/administration/maintain/domain_names.rst:194 msgid "" "To do so, you create a CNAME record for the ``www`` subdomain, with " "``example.odoo.com`` as the target. The DNS zone manager generates the " "following rule and adds it to your DNS zone: ``www IN CNAME " "example.odoo.com.``" msgstr "" #: ../../content/administration/maintain/domain_names.rst:198 msgid "" "You also create a redirection from ``example.com`` to ``wwww.example.com``." msgstr "" #: ../../content/administration/maintain/domain_names.rst:200 msgid "Your new DNS records are propagated to all DNS servers." msgstr "" #: ../../content/administration/maintain/domain_names.rst:203 msgid "Here are some specific guidelines to create a CNAME record:" msgstr "" #: ../../content/administration/maintain/domain_names.rst:205 msgid "`GoDaddy `_" msgstr "" #: ../../content/administration/maintain/domain_names.rst:206 msgid "" "`Namecheap " "`_" msgstr "" #: ../../content/administration/maintain/domain_names.rst:207 msgid "" "`OVH " "`_" msgstr "" #: ../../content/administration/maintain/domain_names.rst:208 msgid "" "`CloudFlare `_" msgstr "" "`CloudFlare `_" #: ../../content/administration/maintain/domain_names.rst:209 msgid "" "`Google Domains `_" msgstr "`구글 도메인 `_" #: ../../content/administration/maintain/domain_names.rst:214 msgid "Naked domain" msgstr "" #: ../../content/administration/maintain/domain_names.rst:216 msgid "" "A **naked domain** is a domain name that doesn't have any subdomain at the " "beginning of the address (e.g., ``odoo.com`` instead of ``www.odoo.com``)." msgstr "" #: ../../content/administration/maintain/domain_names.rst:219 msgid "" "You may want your naked domain to redirect to your website as some visitors " "may not type the full domain name to access your website." msgstr "" #: ../../content/administration/maintain/domain_names.rst:223 msgid "" "Create a **redirection** from the naked domain (``example.com``) to your " "main domain name (``www.example.com``)." msgstr "" #: ../../content/administration/maintain/domain_names.rst:227 msgid "" "Depending on your domain name registrar, this redirection may be already " "pre-configured." msgstr "" #: ../../content/administration/maintain/domain_names.rst:232 msgid "Map your domain name with your Odoo database" msgstr "" #: ../../content/administration/maintain/domain_names.rst:238 msgid "" "Open your `database manager `_, click on " "the :guilabel:`settings` button next to your database, on :guilabel:`Domain " "names`, and then on :guilabel:`Use my own domain` at the bottom of the right" " column." msgstr "" #: ../../content/administration/maintain/domain_names.rst:242 msgid "" "Type the domain name you want to add to this database, then click on " ":guilabel:`Verify` to check if the CNAME record is correctly configured. " "Once done, click on :guilabel:`I confirm, it's done`." msgstr "" #: ../../content/administration/maintain/domain_names.rst:0 msgid "" "Verification of the CNAME records of a domain name before mapping it with a " "database" msgstr "" #: ../../content/administration/maintain/domain_names.rst:252 msgid "" "Go to :menuselection:`Branches --> select your branch --> Settings --> " "Custom domains`, type the domain name you want to add to this database, then" " click on :guilabel:`Add domain`." msgstr "" #: ../../content/administration/maintain/domain_names.rst:0 msgid "Mapping a domain name with an Odoo.sh branch" msgstr "" #: ../../content/administration/maintain/domain_names.rst:260 msgid "" ":ref:`Odoo.sh branches: settings tab `" msgstr "" ":ref:`Odoo.sh branches: settings tab `" #: ../../content/administration/maintain/domain_names.rst:263 msgid "" "Make sure to :ref:`add a CNAME record ` to your domain " "name's DNS **before** mapping your domain name with your Odoo database." msgstr "" #: ../../content/administration/maintain/domain_names.rst:266 msgid "" "Failing to do so may impede the validation of the :ref:`SSL certificate " "` and would result in a *certificate name mismatch* error. " "This is often displayed by web browsers as a warning such as *\"Your " "connection is not private\"*." msgstr "" #: ../../content/administration/maintain/domain_names.rst:270 msgid "" "If this is the case and you have added the domain name to your database's " "settings less than five days ago, wait 24 hours as the validation may still " "happen. Otherwise, please `submit a support ticket " "`_ including screenshots of your CNAME records." msgstr "" #: ../../content/administration/maintain/domain_names.rst:277 msgid "SSL encryption (HTTPS protocol)" msgstr "" #: ../../content/administration/maintain/domain_names.rst:279 msgid "" "**SSL encryption** is an encryption-based Internet security protocol. It " "allows your visitors to navigate your website through a secure connection, " "which appears as an ``https://`` protocol at the beginning of your web " "address, rather than a non-secure ``http://`` protocol." msgstr "" #: ../../content/administration/maintain/domain_names.rst:283 msgid "" "Odoo generates a separate SSL certificate for each domain :ref:`mapped in " "the database manager `, using integration with `Let's " "Encrypt Certificate Authority and ACME protocol " "`_." msgstr "" #: ../../content/administration/maintain/domain_names.rst:288 msgid "The certificate generation may take up to 24h." msgstr "" #: ../../content/administration/maintain/domain_names.rst:289 msgid "" "Several attempts to validate your certificate are made during the five days " "following the moment you add your domain name in your database's settings." msgstr "" #: ../../content/administration/maintain/domain_names.rst:291 msgid "" "If you already use another service, you can keep using it or simply change " "for Odoo." msgstr "" #: ../../content/administration/maintain/domain_names.rst:296 msgid "Web base URL of a database" msgstr "" #: ../../content/administration/maintain/domain_names.rst:299 msgid "" "If you have Odoo Website, you can disregard this part and directly :ref:`map" " your domain name with your website `." msgstr "" #: ../../content/administration/maintain/domain_names.rst:302 msgid "" "The **web base URL** of a database, or **root URL** affects your main " "website address and all the links sent to your customers (e.g., quotations, " "portal links, etc.)." msgstr "" #: ../../content/administration/maintain/domain_names.rst:305 msgid "" "To configure it, access your Odoo database with your custom address, then " "log in as an administrator of your database (any user in the *Settings* " "group) from the login screen." msgstr "" #: ../../content/administration/maintain/domain_names.rst:309 msgid "" "Connecting to your database with the original Odoo subdomain address (e.g., " "``example.odoo.com`` also updates the web base URL of your database. See " "below to prevent these automatic updates." msgstr "" #: ../../content/administration/maintain/domain_names.rst:312 msgid "" "Alternatively, you can do it manually. To do so, activate the " ":ref:`developer mode `, then go to :menuselection:`Settings " "--> Technical --> System Parameters`." msgstr "" #: ../../content/administration/maintain/domain_names.rst:315 msgid "" "Find the key called ``web.base.url`` (or create it if it does not exist) and" " enter the full address of your website as value, such as " "``https://www.example.com``." msgstr "" #: ../../content/administration/maintain/domain_names.rst:319 msgid "" "The URL must include the protocol ``https://`` (or ``http://``) and must not" " end with a slash (``/``)." msgstr "" #: ../../content/administration/maintain/domain_names.rst:322 msgid "" "To prevent the automatic update of the web base URL when an administrator " "logs in the database, you can create the following System Parameter:" msgstr "" #: ../../content/administration/maintain/domain_names.rst:325 msgid "key: ``web.base.url.freeze``" msgstr "" #: ../../content/administration/maintain/domain_names.rst:326 msgid "value: ``True``" msgstr "" #: ../../content/administration/maintain/domain_names.rst:331 msgid "Map your domain name with your website" msgstr "" #: ../../content/administration/maintain/domain_names.rst:333 msgid "" "Mapping your domain name to your website isn't the same as mapping it with " "your database:" msgstr "" #: ../../content/administration/maintain/domain_names.rst:335 msgid "" "It defines your domain name as the main one for your website, helping search" " engines to index your website properly." msgstr "" #: ../../content/administration/maintain/domain_names.rst:337 msgid "" "It defines your domain name as the base URL for your database, including the" " portal links sent by email to your customers." msgstr "" #: ../../content/administration/maintain/domain_names.rst:339 msgid "" "If you have multiple websites, it maps your domain name with the appropriate" " website." msgstr "" #: ../../content/administration/maintain/domain_names.rst:341 msgid "" "Go to :menuselection:`Website --> Configuration --> Settings --> Website " "Info`. If you have multiple websites, select the one you want to configure." msgstr "" #: ../../content/administration/maintain/domain_names.rst:344 msgid "" "In the :guilabel:`Domain` field, fill in the web address of your website " "(e.g., ``https://www.example.com``) and click on :guilabel:`Save`." msgstr "" #: ../../content/administration/maintain/domain_names.rst-1 msgid "Configuring https://www.example.com as the Domain of the website" msgstr "" #: ../../content/administration/maintain/domain_names.rst:352 msgid "" "Mapping your domain name with your Odoo website prevents Google from " "indexing both your custom domain name ``www.example.com`` and your original " "odoo database address ``example.odoo.com``." msgstr "" #: ../../content/administration/maintain/domain_names.rst:355 msgid "" "If both addresses are already indexed, it may take some time before Google " "removes the indexation of the second address. You may also try using the " "`Google Search Console `_ to fix " "this." msgstr "" #: ../../content/administration/maintain/domain_names.rst:360 msgid "" "If you have multiple websites and companies on your database, make sure that" " you select the right :guilabel:`Company` in the website settings, next to " "the :guilabel:`Domain` settings. Doing so indicates Odoo which URL to use as" " the :ref:`base URL ` according to the company in " "use." msgstr "" #: ../../content/administration/maintain/domain_names.rst:366 msgid ":doc:`/applications/general/email_communication/email_servers`" msgstr ":doc:`/applications/general/email_communication/email_servers`" #: ../../content/administration/maintain/enterprise.rst:6 msgid "Switch from Community to Enterprise" msgstr "" #: ../../content/administration/maintain/enterprise.rst:8 msgid "" "Depending on your current installation, there are multiple ways to upgrade " "your community version. In any case the basic guidelines are:" msgstr "" #: ../../content/administration/maintain/enterprise.rst:12 #: ../../content/administration/maintain/enterprise.rst:31 #: ../../content/administration/maintain/enterprise.rst:63 #: ../../content/administration/maintain/enterprise.rst:80 msgid "Backup your community database" msgstr "" #: ../../content/administration/maintain/enterprise.rst:17 #: ../../content/administration/maintain/enterprise.rst:62 msgid "Shutdown your server" msgstr "" #: ../../content/administration/maintain/enterprise.rst:19 msgid "Install the web_enterprise module" msgstr "" #: ../../content/administration/maintain/enterprise.rst:21 msgid "Restart your server" msgstr "" #: ../../content/administration/maintain/enterprise.rst:23 msgid "Enter your Odoo Enterprise Subscription code" msgstr "" #: ../../content/administration/maintain/enterprise.rst:29 msgid "On Linux, using an installer" msgstr "" #: ../../content/administration/maintain/enterprise.rst:33 msgid "Stop the odoo service" msgstr "" #: ../../content/administration/maintain/enterprise.rst:39 msgid "" "Install the enterprise .deb (it should install over the community package)" msgstr "" #: ../../content/administration/maintain/enterprise.rst:45 msgid "Update your database to the enterprise packages using" msgstr "" #: ../../content/administration/maintain/enterprise.rst:51 msgid "" "You should be able to connect to your Odoo Enterprise instance using your " "usual mean of identification. You can then link your database with your Odoo" " Enterprise Subscription by entering the code you received by e-mail in the " "form input" msgstr "" #: ../../content/administration/maintain/enterprise.rst:57 msgid "On Linux, using the source code" msgstr "" #: ../../content/administration/maintain/enterprise.rst:59 msgid "" "There are many ways to launch your server when using sources, and you " "probably have your own favourite. You may need to adapt sections to your " "usual workflow." msgstr "" #: ../../content/administration/maintain/enterprise.rst:64 msgid "" "Update the ``--addons-path`` parameter of your launch command (see " ":doc:`../install/source`)" msgstr "" #: ../../content/administration/maintain/enterprise.rst:65 msgid "Install the web_enterprise module by using" msgstr "" #: ../../content/administration/maintain/enterprise.rst:71 msgid "Depending on the size of your database, this may take some time." msgstr "" #: ../../content/administration/maintain/enterprise.rst:73 msgid "" "Restart your server with the updated addons path of point 3. You should be " "able to connect to your instance. You can then link your database with your " "Odoo Enterprise Subscription by entering the code you received by e-mail in " "the form input" msgstr "" #: ../../content/administration/maintain/enterprise.rst:78 msgid "On Windows" msgstr "" #: ../../content/administration/maintain/enterprise.rst:82 msgid "" "Uninstall Odoo Community (using the Uninstall executable in the installation" " folder) - PostgreSQL will remain installed" msgstr "" #: ../../content/administration/maintain/enterprise.rst:88 msgid "" "Launch the Odoo Enterprise Installer and follow the steps normally. When " "choosing the installation path, you can set the folder of the Community " "installation (this folder still contains the PostgreSQL installation). " "Uncheck ``Start Odoo`` at the end of the installation" msgstr "" #: ../../content/administration/maintain/enterprise.rst:96 msgid "" "Using a command window, update your Odoo Database using this command (from " "the Odoo installation path, in the server subfolder)" msgstr "" #: ../../content/administration/maintain/enterprise.rst:103 msgid "" "No need to manually launch the server, the service is running. You should be" " able to connect to your Odoo Enterprise instance using your usual mean of " "identification. You can then link your database with your Odoo Enterprise " "Subscription by entering the code you received by e-mail in the form input" msgstr "" #: ../../content/administration/maintain/google_oauth.rst:3 msgid "Connect Gmail to Odoo using Google OAuth" msgstr "" #: ../../content/administration/maintain/google_oauth.rst:5 msgid "" "Odoo is compatible with Google's OAuth for Gmail. In order to send secure " "emails from a custom domain, all that is required is to configure a few " "settings on Google's *Workspace* platform, as well as on the back end of the" " Odoo database. This configuration works by using either a personal email " "address or an address created by a custom domain." msgstr "" "Odoo는 Google Gmail용 OAuth와 호환됩니다. 사용자 지정 도메인에서 보안 이메일을 보내려면 Google의 *작업 공간* " "플랫폼과 Odoo 데이터베이스의 백엔드에서 몇 가지 설정만 구성하면 됩니다. 해당 설정 내용은 개인 이메일 주소 또는 사용자 지정 " "도메인에서 만든 주소를 활용하여 작동합니다." #: ../../content/administration/maintain/google_oauth.rst:11 msgid "" "For more information, visit `Google's documentation " "`_ on setting up OAuth." msgstr "" #: ../../content/administration/maintain/google_oauth.rst:15 msgid ":doc:`/applications/general/auth/google`" msgstr ":doc:`/applications/general/auth/google`" #: ../../content/administration/maintain/google_oauth.rst:16 msgid ":doc:`/applications/productivity/calendar/google`" msgstr ":doc:`/applications/productivity/calendar/google`" #: ../../content/administration/maintain/google_oauth.rst:19 msgid "Setup in Google" msgstr "Google 설정하기" #: ../../content/administration/maintain/google_oauth.rst:22 msgid "Create a new project" msgstr "" #: ../../content/administration/maintain/google_oauth.rst:24 msgid "" "To get started, go to the `Google API Console " "`_. Log in with your *Google " "Workspace* account if you have one, otherwise log in with your personal " "Gmail account (this should match the email address you want to configure in " "Odoo)." msgstr "" #: ../../content/administration/maintain/google_oauth.rst:28 msgid "" "After that, click on :guilabel:`Create Project`, located on the far right of" " the :guilabel:`OAuth consent screen`. If a project has already been created" " in this account, then the :guilabel:`New Project` option will be located on" " the top right under the :guilabel:`Select a project` drop-down menu." msgstr "" #: ../../content/administration/maintain/google_oauth.rst:33 msgid "" "On the :menuselection:`New Project` screen, rename the :guilabel:`Project " "name` to `Odoo` and browse for the :guilabel:`Location`. Set the " ":guilabel:`Location` as the *Google Workspace organization*. If you are " "using a personal Gmail account, then leave the :guilabel:`Location` as " ":guilabel:`No Organization`." msgstr "" #: ../../content/administration/maintain/google_oauth.rst-1 msgid "Project Name and Location for Google OAuth." msgstr "" #: ../../content/administration/maintain/google_oauth.rst:42 msgid "Click on :guilabel:`Create` to finish this step." msgstr "" #: ../../content/administration/maintain/google_oauth.rst:45 msgid "OAuth consent screen" msgstr "OAuth 동의 화면" #: ../../content/administration/maintain/google_oauth.rst:47 msgid "" "If the page doesn't redirect to the :menuselection:`User Type` options, " "click on :guilabel:`OAuth consent screen` in the left menu." msgstr "" #: ../../content/administration/maintain/google_oauth.rst:50 msgid "" "Under :guilabel:`User Type` options, select the appropriate :guilabel:`User " "Type`, and then click on :guilabel:`Create` again, which will finally " "navigate to the :menuselection:`Edit app registration` page." msgstr "" #: ../../content/administration/maintain/google_oauth.rst:55 msgid "" "*Personal* Gmail Accounts are only allowed to be **External** User Type, " "which means Google may require an approval, or for *Scopes* to be added on. " "However, using a *Google WorkSpace* account allows for **Internal** User " "Type to be used." msgstr "" "Gmail *개인* 계정은 사용자 유형으로 **외부** 항목만 선택하실 수 있으며, Google 승인 후에만 사용할 수 있거나 *범위* " "내용을 추가하셔야 할 수 있습니다. 반면 *Google WorkSpace* 계정을 사용하는 경우에는 사용자 유형을 **내부**로 " "선택하시면 됩니다." #: ../../content/administration/maintain/google_oauth.rst:59 msgid "" "Note, as well, that while the API connection is in the *External* testing " "mode, then no approval is necessary from Google. User limits in this testing" " mode is set to 100 users." msgstr "" "다만, *외부* 테스트 모드에서 API 연결을 하는 경우에는 Google에서 승인을 받을 필요가 없습니다. 해당 테스트 모드에서 사용자 " "설정은 100명으로 제한되어 있습니다." #: ../../content/administration/maintain/google_oauth.rst:63 msgid "Edit app registration" msgstr "" #: ../../content/administration/maintain/google_oauth.rst:65 msgid "Next we will configure the app registration of the project." msgstr "" #: ../../content/administration/maintain/google_oauth.rst:67 msgid "" "On the :guilabel:`OAuth consent screen` step, under the :guilabel:`App " "information` section, enter `Odoo` in the :guilabel:`App name` field. Select" " the organization's email address under the :guilabel:`User support` email " "field." msgstr "" #: ../../content/administration/maintain/google_oauth.rst:71 msgid "" "Next, under :menuselection:`App Domain --> Authorized domains`, click on " ":guilabel:`Add Domain` and enter `odoo.com`." msgstr "" #: ../../content/administration/maintain/google_oauth.rst:74 msgid "" "After that, under the :guilabel:`Developer contact information` section, " "enter the organization's email address. Google uses this email address to " "notify the organization about any changes to your project." msgstr "" #: ../../content/administration/maintain/google_oauth.rst:78 msgid "" "Next, click on the :guilabel:`Save and Continue` button. Then, skip the " ":menuselection:`Scopes` page by scrolling to the bottom and clicking on " ":guilabel:`Save and Continue`." msgstr "" #: ../../content/administration/maintain/google_oauth.rst:81 msgid "" "If continuing in testing mode (External), add the email addresses being " "configured under the :guilabel:`Test users` step, by clicking on " ":guilabel:`Add Users`, and then the :guilabel:`Save and Continue` button. A " "summary of the app registration appears." msgstr "" #: ../../content/administration/maintain/google_oauth.rst:85 msgid "" "Finally, scroll to the bottom and click on :guilabel:`Back to Dashboard` to " "finish setting up the project." msgstr "" #: ../../content/administration/maintain/google_oauth.rst:89 msgid "Create Credentials" msgstr "자격증명 생성" #: ../../content/administration/maintain/google_oauth.rst:91 msgid "" "Now that the project is set up, credentials should be created, which " "includes the *Client ID* and *Client Secret*. First, click on " ":guilabel:`Credentials` in the left sidebar menu." msgstr "" #: ../../content/administration/maintain/google_oauth.rst:94 msgid "" "Then, click on :guilabel:`Create Credentials` in the top menu and select " ":guilabel:`OAuth client ID` from the dropdown menu." msgstr "" #: ../../content/administration/maintain/google_oauth.rst:97 msgid "" "Under :guilabel:`Application Type`, select :guilabel:`Web Application` from " "the dropdown menu." msgstr "" #: ../../content/administration/maintain/google_oauth.rst:98 msgid "In the :guilabel:`Name` field, enter `Odoo`." msgstr "" #: ../../content/administration/maintain/google_oauth.rst:99 msgid "" "Under the :guilabel:`Authorized redirect URIs` label, click the button " ":guilabel:`ADD URI`, and then input " "`https://yourdbname.odoo.com/google_gmail/confirm` in the :guilabel:`URIs 1`" " field. Be sure to replace the *yourdbname* part of the URL with the actual " "Odoo database name." msgstr "" #: ../../content/administration/maintain/google_oauth.rst:102 msgid "" "Next, click on :guilabel:`Create` to generate an OAuth :guilabel:`Client ID`" " and :guilabel:`Client Secret`. Finally, copy each generated value for later" " use when configuring in Odoo, and then navigate to the Odoo database." msgstr "" #: ../../content/administration/maintain/google_oauth.rst-1 msgid "Client ID and Client Secret for Google OAuth." msgstr "" #: ../../content/administration/maintain/google_oauth.rst:114 msgid "Enter Google Credentials" msgstr "" #: ../../content/administration/maintain/google_oauth.rst:116 msgid "" "First, open Odoo and navigate to the :guilabel:`Apps` module. Then, remove " "the :guilabel:`Apps` filter from the search bar and type in `Google`. " "Install the module called :guilabel:`Google Gmail`." msgstr "" #: ../../content/administration/maintain/google_oauth.rst:120 msgid "" "Next, navigate to :menuselection:`Settings --> General Settings`, and under " "the :guilabel:`Discuss` section, ensure that the checkbox for " ":guilabel:`Custom Email Servers` or :guilabel:`External Email Servers` is " "checked. This populates a new option for :guilabel:`Gmail Credentials` or " ":guilabel:`Use a Gmail Sever`. Then, copy and paste the respective values " "into the :guilabel:`Client ID` and :guilabel:`Client Secret` fields and " ":guilabel:`Save` the settings." msgstr "" #: ../../content/administration/maintain/google_oauth.rst:129 msgid "" "To configure the external Gmail account, return to the top of the " ":guilabel:`Custom Email Servers` setting and then click the " ":guilabel:`Outgoing Email Servers` link." msgstr "" #: ../../content/administration/maintain/google_oauth.rst-1 msgid "Configure Outgoing Email Servers in Odoo." msgstr "" #: ../../content/administration/maintain/google_oauth.rst:136 msgid "" "Then, click on :guilabel:`New` or :guilabel:`Create` to create a new email " "server, and fill in the :guilabel:`Name`, :guilabel:`Description`, and the " "email :guilabel:`Username` (if required)." msgstr "" #: ../../content/administration/maintain/google_oauth.rst:139 msgid "" "Next, click on :guilabel:`Gmail OAuth Authentication` or :guilabel:`Gmail` " "(under the :guilabel:`Authenticate with` or :guilabel:`Connection` section)." " Finally, click on :guilabel:`Connect your Gmail Account`." msgstr "" #: ../../content/administration/maintain/google_oauth.rst:143 msgid "" "A new window labeled :guilabel:`Google` opens to complete the authorization " "process. Select the appropriate email address that is being configured in " "Odoo." msgstr "" #: ../../content/administration/maintain/google_oauth.rst:146 msgid "" "If the email address is a personal account, then an extra step pops up, so " "click :guilabel:`Continue` to allow the verification and connect the Gmail " "account to Odoo." msgstr "" #: ../../content/administration/maintain/google_oauth.rst:149 msgid "" "Then, allow Odoo to access the Google account by clicking on " ":guilabel:`Continue` or :guilabel:`Allow`. After that, the page navigates " "back to the newly configured outgoing email server in Odoo. The " "configuration automatically loads the token in Odoo, and a tag stating " ":guilabel:`Gmail Token Valid` appears in green." msgstr "" #: ../../content/administration/maintain/google_oauth.rst:158 msgid "" "Finally, :guilabel:`Test the Connection`. A confirmation message should " "appear. The Odoo database can now send safe, secure emails through Google " "using OAuth authentication." msgstr "" #: ../../content/administration/maintain/google_oauth.rst:162 msgid "Google OAuth FAQ" msgstr "" #: ../../content/administration/maintain/google_oauth.rst:165 msgid "Production VS Testing Publishing Status" msgstr "" #: ../../content/administration/maintain/google_oauth.rst:167 msgid "" "Choosing :guilabel:`Production` as the :guilabel:`Publishing Status` " "(instead of :guilabel:`Testing`) will display the following warning message:" msgstr "" #: ../../content/administration/maintain/google_oauth.rst-1 msgid "OAuth is Limited to 100 Sensitive Scope Logins." msgstr "" #: ../../content/administration/maintain/google_oauth.rst:174 msgid "" "To correct this warning, navigate to the `Google API Platform " "`_. If the " ":guilabel:`Publishing status` is :guilabel:`In Production`, click " ":guilabel:`Back to Testing` to correct the issue." msgstr "" #: ../../content/administration/maintain/google_oauth.rst:179 msgid "No Test Users Added" msgstr "" #: ../../content/administration/maintain/google_oauth.rst:181 msgid "" "If no test users are added to the OAuth consent screen, then a 403 access " "denied error will populate." msgstr "" #: ../../content/administration/maintain/google_oauth.rst-1 msgid "403 Access Denied Error." msgstr "" #: ../../content/administration/maintain/google_oauth.rst:188 msgid "" "To correct this error, return to the :guilabel:`OAuth consent screen` under " ":guilabel:`APIs & Services` and add test user(s) to the app. Add the email " "that you are configuring in Odoo." msgstr "" #: ../../content/administration/maintain/google_oauth.rst:192 msgid "Gmail Module not updated" msgstr "" #: ../../content/administration/maintain/google_oauth.rst:194 msgid "" "If the *Google Gmail* module in Odoo has not been updated to the latest " "version, then a :guilabel:`Forbidden` error message populates." msgstr "" #: ../../content/administration/maintain/google_oauth.rst-1 msgid "" "Forbidden you don't have the permission to access the requested resource." msgstr "" #: ../../content/administration/maintain/google_oauth.rst:201 msgid "" "To correct this error, go to the :menuselection:`Apps` module and clear out " "the search terms. Then, search for `Gmail` or `Google` and upgrade the " ":guilabel:`Google Gmail` module. Finally, click on the three dots on the " "upper right of the module and select :guilabel:`Upgrade`." msgstr "" #: ../../content/administration/maintain/google_oauth.rst:206 msgid "Application Type" msgstr "" #: ../../content/administration/maintain/google_oauth.rst:208 msgid "" "When creating the credentials (OAuth *Client ID* and *Client Secret*), if " ":guilabel:`Desktop App` is selected for the :guilabel:`Application Type`, an" " :guilabel:`Authorization Error` appears." msgstr "" #: ../../content/administration/maintain/google_oauth.rst-1 msgid "Error 400 Redirect URI Mismatch." msgstr "" #: ../../content/administration/maintain/google_oauth.rst:215 msgid "" "To correct this error, delete the credentials already created and create new" " credentials, selecting :guilabel:`Web Application` for the " ":guilabel:`Application Type`. Then, under :guilabel:`Authorized redirect " "URIs`, click :guilabel:`ADD URI` and type: " "`https://yourdbname.odoo.com/google_gmail/confirm` in the field, being sure " "to replace *yourdbname* in the URL with the Odoo database name." msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:3 msgid "Change hosting solution" msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:5 msgid "" "The instructions to change the hosting type of a database depend on the " "current solution used and to which solution the database should be moved." msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:9 msgid "Transferring an on-premise database" msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:12 #: ../../content/administration/maintain/hosting_changes.rst:80 msgid "To Odoo Online" msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:15 #: ../../content/administration/maintain/hosting_changes.rst:83 msgid "Odoo Online is *not* compatible with **non-standard apps**." msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:16 msgid "" "The database's current version must be :doc:`supported " "`." msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:18 msgid "Create a :ref:`duplicate ` of the database." msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:19 msgid "In this duplicate, uninstall all **non-standard apps**." msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:20 msgid "Use the database manager to grab a *dump with filestore*." msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:21 msgid "" "`Submit a support ticket `_ including the " "following:" msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:23 #: ../../content/administration/maintain/hosting_changes.rst:88 msgid "your **subscription number**," msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:24 msgid "" "the **URL** you want to use for the database (e.g., `company.odoo.com`), and" msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:25 msgid "" "the **dump** as an attachment or as a link to the file (required for 60 MB+ " "files)." msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:27 #: ../../content/administration/maintain/hosting_changes.rst:95 msgid "" "Odoo then makes sure the database is compatible before putting it online. In" " case of technical issues during the process, Odoo might contact you." msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:31 #: ../../content/administration/maintain/hosting_changes.rst:99 msgid "" "If you have time constraints, `submit a support ticket " "`_ as soon as possible to schedule the transfer." msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:35 #: ../../content/administration/maintain/hosting_changes.rst:67 msgid "To Odoo.sh" msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:37 #: ../../content/administration/maintain/hosting_changes.rst:73 msgid "" "Follow the instructions found in :ref:`the Import your database section " "` of the Odoo.sh *Create your project* " "documentation." msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:41 msgid "Transferring an Odoo Online database" msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:44 msgid "" "Odoo Online's :ref:`intermediary versions ` cannot be " "hosted on-premise as that type of hosting does not support those versions. " "Therefore, if the database to transfer is running an intermediary version, " "it must be upgraded first to the next :ref:`major version " "`, waiting for its release if necessary." msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:50 msgid "" "Transferring an online database running on Odoo 16.3 would require first " "upgrading it to Odoo 17.0." msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:54 msgid "" "Click the gear icon (:guilabel:`⚙`) next to the database name on the `Odoo " "Online database manager `_ to display " "its version number." msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:58 #: ../../content/administration/maintain/hosting_changes.rst:108 msgid "To on-premise" msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:60 #: ../../content/administration/maintain/hosting_changes.rst:69 msgid "" "Sign in to `the Odoo Online database manager " "`_ and click the gear icon " "(:guilabel:`⚙`) next to the database name to :guilabel:`Download` a backup. " "If the download fails due to the file being too large, `contact Odoo support" " `_." msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:64 #: ../../content/administration/maintain/hosting_changes.rst:111 msgid "" "Restore the database from the database manager on your local server using " "the backup." msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:77 msgid "Transferring an Odoo.sh database" msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:85 msgid "" "Uninstall all **non-standard apps** in a staging build before doing it in " "the production build." msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:86 msgid "" "`Create a support ticket `_ including the " "following:" msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:89 msgid "" "the **URL** you want to use for the database (e.g., `company.odoo.com`)," msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:90 msgid "which **branch** should be migrated," msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:91 msgid "" "in which **region** you want the database to be hosted (Americas, Europe, or" " Asia)," msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:92 msgid "which user(s) will be the **administrator(s)**, and" msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:93 msgid "" "**when** (and in which timezone) you want the database to be up and running." msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:101 msgid "Select the **region** closest to most of your users to reduce latency." msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:102 msgid "Future **administrator(s)** must have an Odoo.com account." msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:103 msgid "" "The **date and time** you want the database to be up and running are helpful" " to organize the switch from the Odoo.sh server to the Odoo Online servers." msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:105 msgid "Databases are **not reachable** during their migration." msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:110 msgid "" "Download a :ref:`backup of your Odoo.sh production database " "`." msgstr "" #: ../../content/administration/maintain/mailjet_api.rst:3 msgid "Mailjet API" msgstr "" #: ../../content/administration/maintain/mailjet_api.rst:5 msgid "" "Odoo is compatible with Mailjet's :abbr:`API (Application Programming " "Interface)` for mass mailing. Set up a dedicated mass mailing server through" " Mailjet by configuring settings in the Mailjet account and the Odoo " "database. In some circumstances, settings need to be configured on the " "custom domain's :abbr:`DNS (Domain Name System)` settings as well." msgstr "" #: ../../content/administration/maintain/mailjet_api.rst:11 msgid "Set up in Mailjet" msgstr "" #: ../../content/administration/maintain/mailjet_api.rst:14 msgid "Create API credentials" msgstr "API 자격증명 생성" #: ../../content/administration/maintain/mailjet_api.rst:16 msgid "" "To get started, sign in to the `Mailjet Account Information " "`_ page. Next, navigate to the " ":guilabel:`Senders & Domains` section and click on :guilabel:`SMTP and SEND " "API Settings`." msgstr "" #: ../../content/administration/maintain/mailjet_api.rst-1 msgid "" "SMTP and Send API Settings link in the Senders & Domains section of Mailjet." msgstr "" #: ../../content/administration/maintain/mailjet_api.rst:24 msgid "" "Then, copy the :abbr:`SMTP (Simple Mail Transfer Protocol)` configuration " "settings onto a notepad. They can be found under the " ":guilabel:`Configuration (SMTP only)` section. The :abbr:`SMTP (Simple Mail " "Transfer Protocol)` configuration settings include the server address, the " "security option needed (Use :abbr:`SSL (Secure Sockets Layer)`/:abbr:`TLS " "(Transport Layer Security)`), and the port number. The settings are needed " "to configure Mailjet in Odoo, which is covered in the :ref:`last section " "`." msgstr "" #: ../../content/administration/maintain/mailjet_api.rst:32 msgid "" "`Mailjet: How can I configure my SMTP parameters? " "`_" msgstr "" #: ../../content/administration/maintain/mailjet_api.rst:36 msgid "" "Odoo blocks `port 25` on Odoo Online and Odoo.sh databases. :ref:`See " "reference here `." msgstr "" #: ../../content/administration/maintain/mailjet_api.rst-1 msgid "SMTP configuration from Mailjet." msgstr "" #: ../../content/administration/maintain/mailjet_api.rst:43 msgid "" "Next, click on the button labeled :guilabel:`Retrieve your API credentials` " "to retrieve the Mailjet API credentials." msgstr "" #: ../../content/administration/maintain/mailjet_api.rst:46 msgid "" "Then, click on the eye icon to reveal the :guilabel:`API key`. Copy this key" " to a notepad, as this serves as the :guilabel:`Username` in the Odoo " "configuration. Next, click on the :guilabel:`Generate Secret Key` button to " "generate the :guilabel:`Secret Key`. Copy this key to a notepad, as this " "serves as the :guilabel:`Password` in the Odoo configuration." msgstr "" #: ../../content/administration/maintain/mailjet_api.rst:52 msgid "Add verified sender address(es)" msgstr "" #: ../../content/administration/maintain/mailjet_api.rst:54 msgid "" "The next step is to add a sender address or a domain to the Mailjet account " "settings so that the email address or domain is approved to send emails " "using Mailjet's servers. First, navigate to the `Mailjet Account Information" " `_ page. Next, click on the :guilabel:`Add" " a Sender Domain or Address` link under the :guilabel:`Senders & Domains` " "section." msgstr "" #: ../../content/administration/maintain/mailjet_api.rst-1 msgid "Add a sender domain or address in the Mailjet interface." msgstr "" #: ../../content/administration/maintain/mailjet_api.rst:63 msgid "" "Determine if a sender's email address or the entire domain needs to be added" " to the Mailjet settings. It may be easier to configure the domain as a " "whole if :abbr:`DNS (Domain Name System)` access is available. Jump to the " ":ref:`Add a domain ` section for steps on " "adding the domain." msgstr "" #: ../../content/administration/maintain/mailjet_api.rst:69 msgid "" "Either all email addresses of the Odoo database users who are sending emails" " using Mailjet's servers need to be configured or the domain(s) of the " "users' email addresses can be configured." msgstr "" #: ../../content/administration/maintain/mailjet_api.rst:72 msgid "" "By default, the email address originally set up in the Mailjet account is " "added as a trusted sender. To add another email address, click on the button" " labeled :guilabel:`Add a sender address`. Then, add the email address that " "is configured to send from the custom domain." msgstr "" #: ../../content/administration/maintain/mailjet_api.rst:76 msgid "" "At minimum the following email addresses should be set up in the provider " "and verified in Mailjet:" msgstr "" #: ../../content/administration/maintain/mailjet_api.rst:78 msgid "notifications\\@yourdomain.com" msgstr "" #: ../../content/administration/maintain/mailjet_api.rst:79 msgid "bounce\\@yourdomain.com" msgstr "" #: ../../content/administration/maintain/mailjet_api.rst:80 msgid "catchall\\@yourdomain.com" msgstr "" #: ../../content/administration/maintain/mailjet_api.rst:83 msgid "" "Replace `yourdomain` with the custom domain for the Odoo database. If there " "isn't one, then use the :guilabel:`mail.catchall.domain` system parameter." msgstr "" #: ../../content/administration/maintain/mailjet_api.rst:86 msgid "" "After that, fill out the :guilabel:`Email Information` form, making sure to " "select the appropriate email type: transactional email or mass emails. After" " completing the form, an activation email is sent to the email address and " "the trusted sender can be activated." msgstr "" #: ../../content/administration/maintain/mailjet_api.rst:90 msgid "" "It is recommended to set up the :abbr:`SPF (Sender Policy " "Framework)`/:abbr:`DKIM (DomainKeys Identified Mail)`/:abbr:`DMARC (Domain-" "based Message Authentication, Reporting, and Conformance)` settings on the " "domain of the sender." msgstr "" #: ../../content/administration/maintain/mailjet_api.rst:95 #: ../../content/administration/maintain/mailjet_api.rst:162 msgid "" "`Mailjet's SPF/DKIM/DMARC documentation " "`_" msgstr "" #: ../../content/administration/maintain/mailjet_api.rst:99 msgid "" "If the database is not using a custom domain, then in order to verify the " "sender's address, a temporary alias (of the three email addresses mentioned " "above) should be set up in Odoo CRM to create a lead. Then, the database is " "able to receive the verification email and verify the accounts." msgstr "" #: ../../content/administration/maintain/mailjet_api.rst:107 msgid "Add a domain" msgstr "" #: ../../content/administration/maintain/mailjet_api.rst:109 msgid "" "By adding an entire domain to the Mailjet account, all the sender addresses " "related to that domain are automatically validated for sending emails using " "Mailjet servers. First, navigate to the `Mailjet Account Information " "`_ page. Next, click on :guilabel:`Add a " "Sender Domain or Address` link under the :guilabel:`Senders & Domains` " "section. Then, click on :guilabel:`Add domain` to add the custom domain." msgstr "" #: ../../content/administration/maintain/mailjet_api.rst:116 msgid "" "The domain needs to be added to the Mailjet account and then validated " "through the :abbr:`DNS (Domain Name System)`." msgstr "" #: ../../content/administration/maintain/mailjet_api.rst:119 msgid "" "After that, fill out the :guilabel:`Add a new Domain` page on Mailjet and " "click :guilabel:`Continue`." msgstr "" #: ../../content/administration/maintain/mailjet_api.rst:122 msgid "" "After adding the domain, a validation page will populate. Unless the Odoo " "database is on-premise (in which case, choose :guilabel:`Option 1`), choose " ":guilabel:`Option 2: Create a DNS Record`. Copy the TXT record information " "to a notepad and then navigate to the domain's :abbr:`DNS (Domain Name " "System)` provider to complete validation." msgstr "" #: ../../content/administration/maintain/mailjet_api.rst-1 msgid "The TXT record information to input on the domain's DNS." msgstr "" #: ../../content/administration/maintain/mailjet_api.rst:132 msgid "Setup in the domain's DNS" msgstr "" #: ../../content/administration/maintain/mailjet_api.rst:134 msgid "" "After getting the TXT record information from the Mailjet account, add a TXT" " record to the domain's :abbr:`DNS (Domain Name System)`. This process " "varies depending on the :abbr:`DNS (Domain Name System)` provider. Consult " "the provider for specific configuration processes. The TXT record " "information consists of the :guilabel:`Host` and :guilabel:`Value`. Paste " "these into the corresponding fields in the TXT record." msgstr "" #: ../../content/administration/maintain/mailjet_api.rst:141 msgid "Return to Mailjet account information" msgstr "" #: ../../content/administration/maintain/mailjet_api.rst:143 msgid "" "After adding the TXT record to the domain's :abbr:`DNS (Domain Name " "System)`, navigate back to the Mailjet account. Then, navigate to " ":menuselection:`Account Information --> Add a Sender Domain or Address`, " "click the gear icon next to :guilabel:`Domain`, and select " ":guilabel:`Validate`." msgstr "" #: ../../content/administration/maintain/mailjet_api.rst:147 msgid "" "This action can also be done by going to the `Sender domains & addresses " "`_ page on the Mailjet account " "information and clicking on :guilabel:`Manage`." msgstr "" #: ../../content/administration/maintain/mailjet_api.rst:150 msgid "" "Next, click :guilabel:`Check Now` to validate the TXT record that was added " "on the domain. A success screen will appear if the domain is configured " "correctly." msgstr "" #: ../../content/administration/maintain/mailjet_api.rst-1 msgid "Check DNS record in Mailjet." msgstr "" #: ../../content/administration/maintain/mailjet_api.rst:157 msgid "" "After successfully setting up the domain, there is an option to " ":guilabel:`Authenticate this domain (SPF/DKIM)`. This button populates " ":abbr:`SPF (Sender Policy Framework)` & :abbr:`DKIM (DomainKeys Identified " "Mail) records to input into the :abbr:`DNS (Domain Name System)` provider." msgstr "" #: ../../content/administration/maintain/mailjet_api.rst-1 msgid "Authenticate the domain with SPF/DKIM records in Mailjet." msgstr "" #: ../../content/administration/maintain/mailjet_api.rst:172 msgid "Set up in Odoo" msgstr "" #: ../../content/administration/maintain/mailjet_api.rst:174 msgid "" "To complete the setup, navigate to the Odoo database and go to the " ":guilabel:`Settings`. With :ref:`developer-mode` turned on, go to the " ":menuselection:`Technical Menu --> Email --> Outgoing Mail Servers`. Then, " "create a new outgoing server configuration by clicking on the " ":guilabel:`Create` button." msgstr "" #: ../../content/administration/maintain/mailjet_api.rst:179 msgid "" "Next, input the `SMTP server` (in-v3.mailjet.com), `port number` (587 or " "465), and `Security (SSL/TLS)` that was copied earlier from the Mailjet " "account. They can also be found `here " "`_. It is recommended to use " ":abbr:`SSL (Secure Sockets Layer)`/:abbr:`TLS (Transport Layer Security)` " "even though Mailjet may not require it." msgstr "" #: ../../content/administration/maintain/mailjet_api.rst:184 msgid "" "For the :guilabel:`Username`, input the :guilabel:`API KEY`. For the " ":guilabel:`Password`, input the :guilabel:`SECRET KEY` that was copied from " "the Mailjet account to the notepad earlier. These settings can be found on " ":menuselection:`Mailjet --> Account Settings --> SMTP and SEND API " "Settings`." msgstr "" #: ../../content/administration/maintain/mailjet_api.rst:189 msgid "" "Then, if the Mailjet server is used for mass emailing, set the " ":guilabel:`Priority` value higher than that of any transactional email " "server(s). Finally, save the settings and :guilabel:`Test the Connection`." msgstr "" #: ../../content/administration/maintain/mailjet_api.rst-1 msgid "Odoo outgoing email server settings." msgstr "" #: ../../content/administration/maintain/mailjet_api.rst:198 msgid "" "In order for the notifications feature to work using Mailjet, there are " "three settings that need to be set in Odoo." msgstr "" #: ../../content/administration/maintain/mailjet_api.rst:201 msgid "" "The :guilabel:`From Filter` needs to be set on the server configuration. It " "is recommended to set it as a domain and not a full email address. It should" " match the domain in the two proceeding steps. More information can be " "referenced :ref:`here `." msgstr "" #: ../../content/administration/maintain/mailjet_api.rst:205 msgid "" "The :guilabel:`mail.default.from` system parameter must have the value " "`notifications\\@yourdomain.com`." msgstr "" #: ../../content/administration/maintain/mailjet_api.rst:207 msgid "" "The :guilabel:`mail.default.from_filter` system parameter must have the " "value `yourdomain.com`. Replace `yourdomain` with the custom domain for the " "Odoo database. If there isn't one, then use the " ":guilabel:`mail.catchall.domain` system parameter." msgstr "" #: ../../content/administration/maintain/mailjet_api.rst:211 msgid "" "For more information see :ref:`Using a default email address " "`." msgstr "" #: ../../content/administration/maintain/mailjet_api.rst:213 msgid "" "The :guilabel:`System Parameters` can be accessed by activating " ":doc:`../../applications/general/developer_mode` in the " ":menuselection:`Settings --> Technical --> Parameters --> System Parameters`" " menu." msgstr "" #: ../../content/administration/maintain/mailjet_api.rst:217 msgid "" "Once the setup is complete, the Odoo database is ready to use the Mailjet " "email server for mass mailing or transactional emails!" msgstr "" #: ../../content/administration/maintain/odoo_online.rst:3 msgid "Odoo Online database management" msgstr "" #: ../../content/administration/maintain/odoo_online.rst:5 msgid "" "To manage a database, go to the `database manager " "`_ and sign in as the database " "administrator." msgstr "" #: ../../content/administration/maintain/odoo_online.rst:8 msgid "" "All the main database management options are available by clicking the " "database name, except the upgrade option, which can be accessed by clicking " "the **arrow in a circle** icon next to the database name. It is only " "displayed if an upgrade is available." msgstr "" #: ../../content/administration/maintain/odoo_online.rst-1 msgid "Accessing the database management options" msgstr "" #: ../../content/administration/maintain/odoo_online.rst:15 msgid ":ref:`odoo_online/upgrade`" msgstr ":ref:`odoo_online/upgrade`" #: ../../content/administration/maintain/odoo_online.rst:16 msgid ":ref:`odoo_online/duplicate`" msgstr ":ref:`odoo_online/duplicate`" #: ../../content/administration/maintain/odoo_online.rst:17 msgid ":ref:`odoo_online/rename`" msgstr ":ref:`odoo_online/rename`" #: ../../content/administration/maintain/odoo_online.rst:18 msgid ":ref:`odoo_online/download`" msgstr ":ref:`odoo_online/download`" #: ../../content/administration/maintain/odoo_online.rst:19 msgid ":ref:`odoo_online/domains`" msgstr ":ref:`odoo_online/domains`" #: ../../content/administration/maintain/odoo_online.rst:20 msgid ":ref:`odoo_online/tags`" msgstr ":ref:`odoo_online/tags`" #: ../../content/administration/maintain/odoo_online.rst:21 msgid ":ref:`odoo_online/delete`" msgstr ":ref:`odoo_online/delete`" #: ../../content/administration/maintain/odoo_online.rst:22 msgid ":ref:`odoo_online/contact-support`" msgstr ":ref:`odoo_online/contact-support`" #: ../../content/administration/maintain/odoo_online.rst:23 msgid ":ref:`odoo_online/users`" msgstr ":ref:`odoo_online/users`" #: ../../content/administration/maintain/odoo_online.rst:28 #: ../../content/administration/odoo_sh/getting_started/branches.rst:293 #: ../../content/administration/odoo_sh/getting_started/settings.rst:77 #: ../../content/administration/odoo_sh/getting_started/settings.rst:113 #: ../../content/administration/upgrade.rst:3 msgid "Upgrade" msgstr "업그레이드" #: ../../content/administration/maintain/odoo_online.rst:30 msgid "Trigger a database upgrade." msgstr "" #: ../../content/administration/maintain/odoo_online.rst:33 msgid "" "For more information about the upgrade process, check out the :ref:`Odoo " "Online upgrade documentation `." msgstr "" #: ../../content/administration/maintain/odoo_online.rst:39 msgid "Duplicate" msgstr "복사" #: ../../content/administration/maintain/odoo_online.rst:41 msgid "" "Create an exact copy of the database, which can be used to perform testing " "without compromising daily operations." msgstr "" #: ../../content/administration/maintain/odoo_online.rst:45 msgid "" "By checking :guilabel:`For testing purposes`, all external actions (emails, " "payments, delivery orders, etc.) are disabled by default on the duplicated " "database." msgstr "" #: ../../content/administration/maintain/odoo_online.rst:47 msgid "Duplicated databases expire automatically after 15 days." msgstr "" #: ../../content/administration/maintain/odoo_online.rst:52 msgid "Rename" msgstr "이름 바꾸기" #: ../../content/administration/maintain/odoo_online.rst:54 msgid "Rename the database and its URL." msgstr "" #: ../../content/administration/maintain/odoo_online.rst:59 msgid "Download" msgstr "다운로드" #: ../../content/administration/maintain/odoo_online.rst:61 msgid "Download a ZIP file containing a backup of the database." msgstr "" #: ../../content/administration/maintain/odoo_online.rst:64 msgid "" "Databases are backed up daily as per the `Odoo Cloud Hosting SLA " "`_." msgstr "" #: ../../content/administration/maintain/odoo_online.rst:72 msgid "" "Use a custom :doc:`domain name ` to access the database via " "another URL." msgstr "" #: ../../content/administration/maintain/odoo_online.rst:75 msgid "" "You can :ref:`register a domain name for free `." msgstr "" #: ../../content/administration/maintain/odoo_online.rst:80 msgid "Tags" msgstr "태그" #: ../../content/administration/maintain/odoo_online.rst:82 msgid "Add tags to easily identify and sort your databases." msgstr "" #: ../../content/administration/maintain/odoo_online.rst:85 msgid "You can search for tags in the search bar." msgstr "" #: ../../content/administration/maintain/odoo_online.rst:90 #: ../../content/administration/odoo_sh/getting_started/branches.rst:550 msgid "Delete" msgstr "삭제" #: ../../content/administration/maintain/odoo_online.rst:92 msgid "Delete a database instantly." msgstr "" #: ../../content/administration/maintain/odoo_online.rst:95 msgid "" "Deleting a database means that all data is permanently lost. The deletion is" " instant and applies to all users. It is recommended to create a backup of " "the database before deleting it." msgstr "" #: ../../content/administration/maintain/odoo_online.rst:98 msgid "" "Carefully read the warning message and only proceed if the implications of " "deleting a database are fully understood." msgstr "" #: ../../content/administration/maintain/odoo_online.rst-1 msgid "The warning message displayed before deleting a database" msgstr "" #: ../../content/administration/maintain/odoo_online.rst:105 msgid "Only an administrator can delete a database." msgstr "" #: ../../content/administration/maintain/odoo_online.rst:106 msgid "The database name is immediately made available to anyone." msgstr "" #: ../../content/administration/maintain/odoo_online.rst:107 msgid "" "Deleting a database if it has expired or is linked to a subscription is " "impossible. In that case, contact `Odoo Support " "`_." msgstr "" #: ../../content/administration/maintain/odoo_online.rst:113 msgid "Contact us" msgstr "문의하기" #: ../../content/administration/maintain/odoo_online.rst:115 msgid "" "Access the `Odoo.com support page `_ with the " "database's details already pre-filled." msgstr "" #: ../../content/administration/maintain/odoo_online.rst:121 msgid "Invite / remove users" msgstr "" #: ../../content/administration/maintain/odoo_online.rst:123 msgid "" "To invite users, fill out the new user's email address and click " ":guilabel:`Invite`. To add multiple users, click :guilabel:`Add more users`." msgstr "" #: ../../content/administration/maintain/odoo_online.rst-1 msgid "Inviting a user on a database" msgstr "" #: ../../content/administration/maintain/odoo_online.rst:129 msgid "To remove users, select them and click :guilabel:`Remove`." msgstr "" #: ../../content/administration/maintain/odoo_online.rst:132 msgid ":doc:`/applications/general/users/manage_users`" msgstr ":doc:`/applications/general/users/manage_users`" #: ../../content/administration/maintain/odoo_online.rst:133 msgid ":doc:`/applications/general/users/odoo_account`" msgstr ":doc:`/applications/general/users/odoo_account`" #: ../../content/administration/maintain/on_premise.rst:3 msgid "On-premise database management" msgstr "" #: ../../content/administration/maintain/on_premise.rst:6 msgid "Register a database" msgstr "" #: ../../content/administration/maintain/on_premise.rst:8 msgid "" "To register your database, you just need to enter your Subscription Code in " "the banner in the App Switcher. Make sure you do not add extra spaces before" " or after your subscription code. If the registration is successful, it will" " turn green and will provide you with the Expiration Date of your freshly-" "registered database. You can check this Expiration Date in the About menu " "(Odoo 9) or in the Settings Dashboard (Odoo 10)." msgstr "" "데이터베이스를 등록하려면 앱 전환기에 있는 배너에 구독 코드를 입력합니다. 구독 코드 앞뒤에 추가 공백이 없는지 확인하세요. 등록에 " "성공하면 배너가 녹색으로 바뀌고 최근에 등록한 데이터베이스의 만료일이 표시됩니다. 이 만료일은 정보 메뉴(Odoo 9) 또는 설정 " "대시보드(Odoo 10)에서 확인할 수 있습니다." #: ../../content/administration/maintain/on_premise.rst:16 msgid "Registration Error Message" msgstr "" #: ../../content/administration/maintain/on_premise.rst:18 msgid "" "If you are unable to register your database, you will likely encounter this " "message:" msgstr "" #: ../../content/administration/maintain/on_premise.rst-1 msgid "" "Something went wrong while registering your database, you can try again or contact Odoo\n" "Help" msgstr "" #: ../../content/administration/maintain/on_premise.rst:27 #: ../../content/administration/maintain/on_premise.rst:100 #: ../../content/administration/maintain/on_premise.rst:127 msgid "Solutions" msgstr "" #: ../../content/administration/maintain/on_premise.rst:29 msgid "Do you have a valid Enterprise subscription?" msgstr "" #: ../../content/administration/maintain/on_premise.rst:31 msgid "" "Check if your subscription details get the tag \"In Progress\" on your `Odoo" " Account `__ or with your Account" " Manager" msgstr "" #: ../../content/administration/maintain/on_premise.rst:35 msgid "Have you already linked a database with your subscription reference?" msgstr "" #: ../../content/administration/maintain/on_premise.rst:37 msgid "" "You can link only one database per subscription. (Need a test or a " "development database? `Find a partner `__)" msgstr "" #: ../../content/administration/maintain/on_premise.rst:41 msgid "" "You can unlink the old database yourself on your `Odoo Contract " "`__ with the button \"Unlink " "database\"" msgstr "" #: ../../content/administration/maintain/on_premise.rst:47 msgid "" "A confirmation message will appear; make sure this is the correct database " "as it will be deactivated shortly:" msgstr "" #: ../../content/administration/maintain/on_premise.rst:53 msgid "Do you have the updated version of Odoo 9?" msgstr "" #: ../../content/administration/maintain/on_premise.rst:55 #: ../../content/administration/maintain/on_premise.rst:159 msgid "" "From July 2016 onward, Odoo 9 now automatically change the uuid of a " "duplicated database; a manual operation is no longer required." msgstr "" #: ../../content/administration/maintain/on_premise.rst:58 msgid "" "If it's not the case, you may have multiple databases sharing the same UUID." " Please check on your `Odoo Contract " "`__, a short message will appear " "specifying which database is problematic:" msgstr "" #: ../../content/administration/maintain/on_premise.rst:66 msgid "" "In this case, you need to change the UUID on your test databases to solve " "this issue. You will find more information about this in :ref:`this section " "`." msgstr "" #: ../../content/administration/maintain/on_premise.rst:69 msgid "" "For your information, we identify database with UUID. Therefore, each " "database should have a distinct UUID to ensure that registration and " "invoicing proceed effortlessly for your and for us." msgstr "" #: ../../content/administration/maintain/on_premise.rst:73 msgid "Check your network and firewall settings" msgstr "" #: ../../content/administration/maintain/on_premise.rst:75 msgid "" "The Update notification must be able to reach Odoo's subscription validation" " servers. In other words, make sure that the Odoo server is able to open " "outgoing connections towards:" msgstr "" #: ../../content/administration/maintain/on_premise.rst:79 msgid "services.odoo.com on port 443 (or 80)" msgstr "" #: ../../content/administration/maintain/on_premise.rst:80 msgid "services.openerp.com on port 443 (or 80) for older deployments" msgstr "" #: ../../content/administration/maintain/on_premise.rst:82 msgid "" "Once you activated your database, you must keep these ports open, as the " "Update notification runs once a week." msgstr "" #: ../../content/administration/maintain/on_premise.rst:86 msgid "Error message due to too many users" msgstr "" #: ../../content/administration/maintain/on_premise.rst:88 msgid "" "If you have more users in your local database than provisionned in your Odoo" " Enterprise subscription, you may encounter this message:" msgstr "" #: ../../content/administration/maintain/on_premise.rst-1 msgid "" "This database will expire in X days, you have more users than your " "subscription allows" msgstr "" #: ../../content/administration/maintain/on_premise.rst:96 msgid "" "When the message appears you have 30 days before the expiration. The " "countdown is updated everyday." msgstr "" #: ../../content/administration/maintain/on_premise.rst:102 msgid "" "**Add more users** on your subscription: follow the link and Validate the " "upsell quotation and pay for the extra users." msgstr "" #: ../../content/administration/maintain/on_premise.rst:104 msgid "" "**Deactivate users** as explained in this `documentation " "`_ and **Reject** the upsell " "quotation." msgstr "" " `문서`_ 에서 기술되어 있는 바와 같이**사용자 비활성화**를 " "실행하고 상향 판매 견적은 **거부**됩니다." #: ../../content/administration/maintain/on_premise.rst:107 msgid "" "Once your database has the correct number of users, the expiration message " "will disappear automatically after a few days, when the next verification " "occurs. We understand that it can be a bit frightening to see the countdown," " so you can :ref:`force an Update Notification ` to make the " "message disappear right away." msgstr "" "데이터베이스 사용자 수가 올바른 경우에는, 다음 인증 시 만료 메시지가 며칠 후 자동으로 사라집니다. 카운트다운이 표시되는 불안한 상황을" " 피하고자 하는 경우에는, :ref:`업데이트 알림 강제 실행 `으로 메시지가 즉시 사라지게 할 수 있습니다." #: ../../content/administration/maintain/on_premise.rst:114 msgid "Database expired error message" msgstr "데이터베이스 만료 오류 메시지" #: ../../content/administration/maintain/on_premise.rst:116 msgid "" "If your database reaches its expiration date before your renew your " "subscription, you will encounter this message:" msgstr "구독 갱신을 하기 전에 데이터베이스 날짜가 만료되면 다음의 메시지가 표시됩니다." #: ../../content/administration/maintain/on_premise.rst-1 msgid "This database has expired." msgstr "이 데이터베이스는 만료되었습니다." #: ../../content/administration/maintain/on_premise.rst:123 msgid "" "This **blocking** message appears after a non-blocking message that lasts 30" " days. If you fail to take action before the end of the countdown, the " "database is expired." msgstr "" "이 **차단** 메시지는 차단되지 않는다는 메시지가 30일 동안 표시된 후 나타납니다. 카운트다운이 종료되기 전에 조치를 취하지 않으면 " "데이터베이스가 만료됩니다." #: ../../content/administration/maintain/on_premise.rst:131 msgid "" "Renew your subscription: follow the link and renew your subscription - note " "that" msgstr "구독 갱신: 링크를 따라 가시면 구독을 갱신할 수 있습니다. 다음에 유의하세요." #: ../../content/administration/maintain/on_premise.rst:130 msgid "" "if you wish to pay by Wire Transfer, your subscription will effectively be " "renewed only when the payment arrives, which can take a few days. Credit " "card payments are processed immediately." msgstr "" "온라인 이체 방식으로 결제하는 경우, 구독은 결제 입금 확인이 된 후에만 유효하게 갱신되며, 입금되기까지 며칠 정도 소요될 수 있습니다." " 신용카드 결제는 즉시 처리됩니다." #: ../../content/administration/maintain/on_premise.rst:133 msgid "Contact our `Support `__" msgstr "`고객 지원 `__으로 연락하시기 바랍니다." #: ../../content/administration/maintain/on_premise.rst:135 msgid "" "None of those solutions worked for you? Please contact our `Support " "`__" msgstr "꼭 맞는 솔루션을 아직 찾지 못하셨나요? `고객 지원 `__으로 문의하세요." #: ../../content/administration/maintain/on_premise.rst:143 msgid "Duplicate a database" msgstr "데이터베이스 복사" #: ../../content/administration/maintain/on_premise.rst:145 msgid "" "You can duplicate your database by accessing the database manager on your " "server (/web/database/manager). In this page, you can easily " "duplicate your database (among other things)." msgstr "" "서버 데이터베이스 관리자(/web/database/manager)로 액세스하여 데이터베이스를 복사할 수 있습니다." " 이 페이지에서는 데이터베이스를 쉽게 복사할 수 있습니다 (다른 내용보다도)." #: ../../content/administration/maintain/on_premise.rst:152 msgid "" "When you duplicate a local database, it is **strongly** advised to change " "the duplicated database's uuid (Unniversally Unique Identifier), since this " "uuid is how your database identifies itself with our servers. Having two " "databases with the same uuid could result in invoicing problems or " "registration problems down the line." msgstr "" "로컬 데이터베이스를 복사하는 경우, 복사한 데이터베이스의 고유 식별 번호 (UUID: Universally Unique " "Identifier)를 변경할 것을 **강력** 권장하며, 이는 해당 데이터베이스를 서버에서 식별하는 방법이 UUID이기 때문입니다. " "동일한 UUID를 가진 두 개의 데이터베이스가 있을 경우 청구서 발행 문제나 등록 문제가 발생할 수 있습니다." #: ../../content/administration/maintain/on_premise.rst:162 msgid "" "The database uuid is currently accessible from the menu " ":menuselection:`Settings --> Technical --> System Parameters`, we advise you" " to use a `uuid generator `_ or to use the unix " "command ``uuidgen`` to generate a new uuid. You can then simply replace it " "like any other record by clicking on it and using the edit button." msgstr "" "데이터베이스 UUID는 현재 :menuselection:`설정 --> 기술 --> 시스템 매개변수`에서 액세스할 수 있습니다. `UUID" " 생성기 `_를 사용하거나 유닉스 명령어 ``uuidgen``을 사용하여 새로운 " "UUID를 생성하는 것이 좋습니다. 그런 다음 해당 레코드를 클릭하고 편집 버튼을 사용하여 다른 레코드처럼 간단히 변경할 수 있습니다." #: ../../content/administration/maintain/supported_versions.rst:7 msgid "Supported versions" msgstr "지원되는 버전" #: ../../content/administration/maintain/supported_versions.rst:9 msgid "" "Odoo provides support and bug fixing **for the 3 last major versions** of " "Odoo." msgstr "" #: ../../content/administration/maintain/supported_versions.rst:12 msgid "" "Odoo releases intermediary versions called **Online versions** on the " ":doc:`Odoo Online ` hosting every two months. Odoo Online users" " can then benefit from the latest features of Odoo." msgstr "" #: ../../content/administration/maintain/supported_versions.rst:16 msgid "" "Admins of Odoo Online databases are invited to :doc:`upgrade <../upgrade>` " "them regularly." msgstr "" #: ../../content/administration/maintain/supported_versions.rst:17 msgid "" "Online versions are *not* released for Odoo.sh and On-Premise installations." msgstr "" #: ../../content/administration/maintain/supported_versions.rst:18 msgid "Online versions are listed below as *SaaS*." msgstr "" #: ../../content/administration/maintain/supported_versions.rst:20 msgid "This matrix shows the support status of every version." msgstr "" #: ../../content/administration/maintain/supported_versions.rst:22 msgid "**Major releases are in bold type.**" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:31 msgid "On-Premise" msgstr "온프레미스" #: ../../content/administration/maintain/supported_versions.rst:32 msgid "Release date" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:33 msgid "End of support" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:34 msgid "**Odoo 17.0**" msgstr "**Odoo 17.0**" #: ../../content/administration/maintain/supported_versions.rst:35 #: ../../content/administration/maintain/supported_versions.rst:36 #: ../../content/administration/maintain/supported_versions.rst:37 #: ../../content/administration/maintain/supported_versions.rst:41 #: ../../content/administration/maintain/supported_versions.rst:65 #: ../../content/administration/maintain/supported_versions.rst:66 #: ../../content/administration/maintain/supported_versions.rst:67 #: ../../content/administration/maintain/supported_versions.rst:83 #: ../../content/administration/maintain/supported_versions.rst:84 #: ../../content/administration/maintain/supported_versions.rst:85 #: ../../content/administration/odoo_sh/getting_started/settings.rst:58 #: ../../content/administration/odoo_sh/getting_started/settings.rst:59 #: ../../content/administration/odoo_sh/getting_started/settings.rst:62 #: ../../content/administration/odoo_sh/getting_started/settings.rst:63 #: ../../content/administration/odoo_sh/getting_started/settings.rst:66 #: ../../content/administration/odoo_sh/getting_started/settings.rst:67 #: ../../content/administration/odoo_sh/getting_started/settings.rst:70 #: ../../content/administration/odoo_sh/getting_started/settings.rst:71 #: ../../content/administration/odoo_sh/getting_started/settings.rst:74 #: ../../content/administration/odoo_sh/getting_started/settings.rst:75 #: ../../content/administration/odoo_sh/getting_started/settings.rst:78 #: ../../content/administration/odoo_sh/getting_started/settings.rst:79 #: ../../content/administration/odoo_sh/getting_started/settings.rst:82 #: ../../content/administration/odoo_sh/getting_started/settings.rst:83 #: ../../content/administration/odoo_sh/getting_started/settings.rst:86 #: ../../content/administration/odoo_sh/getting_started/settings.rst:87 #: ../../content/administration/odoo_sh/getting_started/settings.rst:91 #: ../../content/administration/odoo_sh/getting_started/settings.rst:95 #: ../../content/administration/odoo_sh/getting_started/settings.rst:99 #: ../../content/administration/odoo_sh/getting_started/settings.rst:103 #: ../../content/administration/odoo_sh/getting_started/settings.rst:107 #: ../../content/administration/odoo_sh/getting_started/settings.rst:111 #: ../../content/administration/odoo_sh/getting_started/settings.rst:115 #: ../../content/administration/odoo_sh/getting_started/settings.rst:119 #: ../../content/administration/odoo_sh/getting_started/settings.rst:122 #: ../../content/administration/odoo_sh/getting_started/settings.rst:123 #: ../../content/administration/odoo_sh/getting_started/settings.rst:127 msgid "|green|" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:38 #: ../../content/administration/maintain/supported_versions.rst:93 msgid "November 2023" msgstr "2023년 11월" #: ../../content/administration/maintain/supported_versions.rst:39 msgid "November 2026 (planned)" msgstr "2026년 11월 (예정)" #: ../../content/administration/maintain/supported_versions.rst:40 msgid "Odoo saas~16.4" msgstr "Odoo saas~16.4" #: ../../content/administration/maintain/supported_versions.rst:42 #: ../../content/administration/maintain/supported_versions.rst:43 #: ../../content/administration/maintain/supported_versions.rst:48 #: ../../content/administration/maintain/supported_versions.rst:49 #: ../../content/administration/maintain/supported_versions.rst:54 #: ../../content/administration/maintain/supported_versions.rst:55 #: ../../content/administration/maintain/supported_versions.rst:60 #: ../../content/administration/maintain/supported_versions.rst:61 #: ../../content/administration/maintain/supported_versions.rst:72 #: ../../content/administration/maintain/supported_versions.rst:73 #: ../../content/administration/maintain/supported_versions.rst:78 #: ../../content/administration/maintain/supported_versions.rst:79 msgid "N/A" msgstr "해당 없음" #: ../../content/administration/maintain/supported_versions.rst:44 msgid "August 2023" msgstr "2023년 8월" #: ../../content/administration/maintain/supported_versions.rst:46 msgid "Odoo saas~16.3" msgstr "Odoo saas~16.3" #: ../../content/administration/maintain/supported_versions.rst:47 #: ../../content/administration/maintain/supported_versions.rst:53 #: ../../content/administration/maintain/supported_versions.rst:59 #: ../../content/administration/maintain/supported_versions.rst:71 #: ../../content/administration/maintain/supported_versions.rst:77 #: ../../content/administration/maintain/supported_versions.rst:89 #: ../../content/administration/maintain/supported_versions.rst:90 #: ../../content/administration/maintain/supported_versions.rst:91 #: ../../content/administration/maintain/supported_versions.rst:95 #: ../../content/administration/maintain/supported_versions.rst:96 #: ../../content/administration/maintain/supported_versions.rst:97 #: ../../content/administration/maintain/supported_versions.rst:101 #: ../../content/administration/maintain/supported_versions.rst:102 #: ../../content/administration/maintain/supported_versions.rst:103 msgid "|red|" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:50 msgid "June 2023" msgstr "2023년 6월" #: ../../content/administration/maintain/supported_versions.rst:52 msgid "Odoo saas~16.2" msgstr "Odoo saas~16.2" #: ../../content/administration/maintain/supported_versions.rst:56 msgid "March 2023" msgstr "2023년 3월" #: ../../content/administration/maintain/supported_versions.rst:58 msgid "Odoo saas~16.1" msgstr "Odoo saas~16.1" #: ../../content/administration/maintain/supported_versions.rst:62 msgid "February 2023" msgstr "2023년 2월" #: ../../content/administration/maintain/supported_versions.rst:64 msgid "**Odoo 16.0**" msgstr "**Odoo 16.0**" #: ../../content/administration/maintain/supported_versions.rst:68 #: ../../content/administration/maintain/supported_versions.rst:99 msgid "October 2022" msgstr "2022년 10월" #: ../../content/administration/maintain/supported_versions.rst:69 msgid "November 2025 (planned)" msgstr "2025년 11월 (예정)" #: ../../content/administration/maintain/supported_versions.rst:70 msgid "Odoo saas~15.2" msgstr "Odoo saas~15.2" #: ../../content/administration/maintain/supported_versions.rst:74 msgid "March 2022" msgstr "2022년 3월" #: ../../content/administration/maintain/supported_versions.rst:75 msgid "January 2023" msgstr "2023년 1월" #: ../../content/administration/maintain/supported_versions.rst:76 msgid "Odoo saas~15.1" msgstr "Odoo saas~15.1" #: ../../content/administration/maintain/supported_versions.rst:80 msgid "February 2022" msgstr "2022년 2월" #: ../../content/administration/maintain/supported_versions.rst:81 msgid "July 2022" msgstr "2022년 7월" #: ../../content/administration/maintain/supported_versions.rst:82 msgid "**Odoo 15.0**" msgstr "**Odoo 15.0**" #: ../../content/administration/maintain/supported_versions.rst:86 msgid "October 2021" msgstr "2021년 10월" #: ../../content/administration/maintain/supported_versions.rst:87 msgid "November 2024 (planned)" msgstr "2024년 11월 (예정)" #: ../../content/administration/maintain/supported_versions.rst:88 msgid "**Odoo 14.0**" msgstr "**Odoo 14.0**" #: ../../content/administration/maintain/supported_versions.rst:92 msgid "October 2020" msgstr "2020년 10월" #: ../../content/administration/maintain/supported_versions.rst:94 msgid "**Odoo 13.0**" msgstr "**Odoo 13.0**" #: ../../content/administration/maintain/supported_versions.rst:98 msgid "October 2019" msgstr "2019년 10월" #: ../../content/administration/maintain/supported_versions.rst:100 msgid "Older versions" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:104 msgid "Before 2019" msgstr "2019년 이전" #: ../../content/administration/maintain/supported_versions.rst:105 msgid "Before 2022" msgstr "2022년 이전" #: ../../content/administration/maintain/supported_versions.rst:107 msgid "Legend" msgstr "범례" #: ../../content/administration/maintain/supported_versions.rst:109 msgid "|green| Supported version" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:111 msgid "|red| End-of-support" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:113 msgid "N/A Never released for this platform" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:116 msgid "" "Even though we don't support older versions, you can always `upgrade from " "any version `_." msgstr "" #: ../../content/administration/maintain/update.rst:6 msgid "Bugfix updates" msgstr "버그 수정 업데이트" #: ../../content/administration/maintain/update.rst:9 msgid "Introduction" msgstr "소개" #: ../../content/administration/maintain/update.rst:11 msgid "" "In order to benefit from the latest improvements, security fixes, bug " "corrections and performance boosts, you may need to update your Odoo " "installation from time to time." msgstr "" "최신 개선 내용, 보안 수정, 버그 수정 및 성능 향상을 적용 받는 혜택을 받으려면 가끔씩 Odoo 설치 업데이트를 해야 할 수 " "있습니다." #: ../../content/administration/maintain/update.rst:14 msgid "" "This guide only applies when are using Odoo on your own hosting " "infrastructure. If you are using one of the Odoo Cloud solutions, updates " "are automatically performed for you." msgstr "" "본 안내 사항은 자체 호스팅 인프라에서 Odoo를 사용하는 경우에만 적용됩니다. Odoo 클라우드 솔루션 중에서 사용하는 경우 업데이트가" " 자동으로 수행됩니다." #: ../../content/administration/maintain/update.rst:17 msgid "" "The terminology surrounding software updates is often confusing, so here are" " some preliminary definitions:" msgstr "소프트웨어 업데이트와 관련된 용어는 혼동되는 경우가 많으므로 다음과 같이 몇 가지 사전 정의를 안내해 드립니다." #: ../../content/administration/maintain/update.rst:25 msgid "Updating (an Odoo installation)" msgstr "업데이트 (Odoo 설치)" #: ../../content/administration/maintain/update.rst:21 msgid "" "Refers to the process of obtaining the latest revision of the source code " "for your current Odoo Edition. For example, updating your Odoo Enterprise " "13.0 to the latest revision. This does not directly cause any change to the " "contents of your Odoo database, and can be undone by reinstalling the " "previous revision of the source code." msgstr "" "현재 사용 중인 Odoo 에디션에 대한 소스 코드의 최신 버전을 얻는 프로세스를 의미합니다. 예를 들어, Odoo 엔터프라이즈 13.0을" " 최신 버전으로 업데이트하는 것을 뜻합니다. 이 작업때문에 Odoo 데이터베이스 내용이 직접 변경되지는 않으며, 이전 버전의 소스 코드를" " 재설치하여 실행 취소할 수 있습니다." #: ../../content/administration/maintain/update.rst:35 msgid "Upgrading (an Odoo database)" msgstr "업그레이드 (Odoo 데이터베이스)" #: ../../content/administration/maintain/update.rst:28 msgid "" "Refers to a complex data processing operation where the structure and " "contents of your database is permanently altered to make it compatible with " "a new release of Odoo. This operation is irreversible and typically " "accomplished via Odoo's `database upgrade service " "`_, when you decide to switch to a newer release " "of Odoo. Historically, this process has also been known as a \"migration\" " "because it involves moving data around inside the database, even though the " "database may end up at the same physical location after the upgrade." msgstr "" "데이터베이스의 구조 및 내용이 Odoo 새 버전과 호환되도록 영구적으로 변경하는 복잡한 데이터 처리 작업을 의미합니다. 작업은 되돌릴 수" " 없으며, 일반적으로 Odoo 최신 버전으로 전환하기로 결정한 경우 Odoo의 '데이터베이스 업그레이드 서비스 " "`_'를 통해 진행됩니다. 역사적으로 이 프로세스는 업그레이드 후 데이터베이스가 동일한 " "물리적 위치에 있더라도 데이터베이스 내부에서 데이터를 이동하기 때문에 \"마이그레이션\"이라고도 합니다." #: ../../content/administration/maintain/update.rst:37 msgid "" "This page describes the typical steps needed to *update* an Odoo " "installation to the latest version. If you'd like more information about " "upgrading a database, please visit the `Odoo Upgrade page " "`_ instead." msgstr "" "이 페이지에서는 Odoo 설치를 최신 버전으로 *업데이트*하는 데 필요한 일반적인 단계에 대해 설명되어 있습니다. 데이터베이스 " "업그레이드에 대한 자세한 내용은 'Odoo 업그레이드 페이지 `_를 참조하세요." #: ../../content/administration/maintain/update.rst:43 msgid "In a nutshell" msgstr "한 마디로," #: ../../content/administration/maintain/update.rst:45 msgid "" "Updating Odoo is accomplished by simply reinstalling the latest version of " "your Odoo Edition on top of your current installation. This will preserve " "your data without any alteration, as long as you do not uninstall PostgreSQL" " (the database engine that comes with Odoo)." msgstr "" "Odoo를 업데이트하려면, 현재 설치 내용에 최신 버전 Odoo 에디션을 재설치하기만 하면 됩니다. 이렇게 할 경우 Odoo와 함께 " "제공되는 데이터베이스 엔진인 PostgreSQL을 제거하지 않는 한 데이터를 변경하지 않고 보존할 수 있습니다." #: ../../content/administration/maintain/update.rst:49 msgid "" "The main reference for updating is logically our :doc:`installation guide " "<../install>`, which explains the common installation methods." msgstr "" "업데이트에 대해서 주로 참조하실 수 있는 자료로는 논리적으로 일반적인 설치 방법을 설명하는 :doc:`설치 가이드 " "<../install>`가 있습니다." #: ../../content/administration/maintain/update.rst:52 msgid "" "Updating is also most appropriately accomplished by the person who deployed " "Odoo initially, because the procedure is very similar." msgstr "업데이트 절차는 매우 유사하기 때문에 Odoo를 초기 배포했던 담당자가 수행하는 것이 가장 적절합니다." #: ../../content/administration/maintain/update.rst:55 msgid "" "We always recommend to download a complete new up-to-date Odoo version, " "rather than manually applying patches, such as the security patches that " "come with Security Advisories. The patches are mainly provided for " "installations that are heavily customized, or for technical personnel who " "prefer to apply minimal changes temporarily while testing a complete update." msgstr "" "저희는 언제나 최신판 Odoo 버전 전체를 다운로드 받으시는 것이, 보안 안내 사항과 함께 제공해드리는 보안 패치와 같은 서비스 패치를 " "직접 적용하시는 것보다 바람직하다고 권해드리고 있습니다. 설치 항목에 커스터마이징 항목이 극도로 많이 반영된 경우나, 기술 담당자가 전체" " 업데이트 테스트 중에 일시적으로 최소한만 변경하고자 하는 경우에 주로 패치를 사용하게 됩니다. " #: ../../content/administration/maintain/update.rst:64 msgid "Step 1: Download an updated Odoo version" msgstr "1단계: 업데이트된 Odoo 버전 다운로드하기" #: ../../content/administration/maintain/update.rst:66 msgid "" "The central download page is https://www.odoo.com/page/download. If you see " "a \"Buy\" link for the Odoo Enterprise download, make sure you are logged " "into Odoo.com with the same login that is linked to your Odoo Enterprise " "subscription." msgstr "" "메인 다운로드 페이지는 https://www.odoo.com/page/download 입니다. Odoo 엔터프라이즈 다운로드를 하는 " "\"구매\" 링크가 표시되면 Odoo 엔터프라이즈 구독 항목 연결을 할 때 동일한 로그인으로 Odoo.com에 로그인되었는지 확인하세요." #: ../../content/administration/maintain/update.rst:70 msgid "" "Alternatively, you can use the unique download link that was included with " "your Odoo Enterprise purchase confirmation email." msgstr "또는 Odoo 엔터프라이즈 구매 확인 이메일에 있는 고유 다운로드 링크를 사용할 수 있습니다." #: ../../content/administration/maintain/update.rst:73 msgid "" "Downloading an updated version is not necessary if you installed via Github " "(see below)" msgstr "Github를 통해 설치한 경우에는 업데이트된 버전을 다운로드할 필요가 없습니다 (아래 내용 참조)." #: ../../content/administration/maintain/update.rst:77 msgid "Step 2: Make a backup of your database" msgstr "2단계: 데이터베이스 백업 만들기" #: ../../content/administration/maintain/update.rst:79 msgid "" "The update procedure is quite safe and should not alter you data. However " "it's always best to take a full database backup before performing any change" " on your installation, and to store it somewhere safe, on a different " "computer." msgstr "" "업데이트 절차는 매우 안전하며 데이터를 변경하지 안 됩니다. 그러나 설치 변경을 하기 전에 항상 전체 데이터베이스를 백업한 후 다른 " "안전한 컴퓨터에 저장하는 것이 가장 좋습니다." #: ../../content/administration/maintain/update.rst:83 msgid "" "If you have not disabled the database manager screen (see :ref:`here " "` why you should), you can use it (link at bottom of your database" " selection screen) to download a backup of your database(s). If you disabled" " it, use the same procedure than for your usual backups." msgstr "" "데이터베이스 관리자 화면을 비활성화하지 않은 경우 (해야 하는 이유를 :ref:`여기 `에서 참조), 활성화하여 " "(데이터베이스 선택 화면 하단에 있는 링크) 데이터베이스 백업을 다운로드할 수 있습니다. 비활성화한 경우에는 일반적인 백업 절차와 " "동일하게 진행합니다." #: ../../content/administration/maintain/update.rst:89 msgid "Step 3: Install the updated version" msgstr "3단계: 업데이트된 버전 설치" #: ../../content/administration/maintain/update.rst:91 msgid "Choose the method that matches your current installation:" msgstr "현재 설치할 내용에 맞는 방법을 선택합니다." #: ../../content/administration/maintain/update.rst:95 msgid "Packaged Installers" msgstr "설치 패키지 프로그램" #: ../../content/administration/maintain/update.rst:97 msgid "" "If you installed Odoo with an installation package downloaded on our website" " (the recommended method), updating is very simple. All you have to do is " "download the installation package corresponding to your system (see step #1)" " and install it on your server. They are updated daily and include the " "latest security fixes. Usually, you can simply double-click the package to " "install it on top of the current installation. After installing the package," " be sure to restart the Odoo service or reboot your server, and you're all " "set." msgstr "" "웹사이트에서 다운로드한 설치 패키지를 사용하여 Odoo를 설치한 경우 (권장 방법), 업데이트 프로세스는 간단합니다. 시스템에 맞는 설치" " 패키지를 다운로드하고 (1단계 참조) 서버에 설치하기만 하면 됩니다. 이러한 패키지는 매일 업데이트되며 최신 보안 수정 사항이 포함되어" " 있습니다. 일반적으로 패키지를 두 번 클릭하여 설치하면 기존 설치 파일 위에 설치됩니다. 설치가 완료된 후 Odoo 서비스를 다시 " "시작하거나 서버를 재부팅하면 모든 준비가 완료됩니다." #: ../../content/administration/maintain/update.rst:106 msgid "Source Install (Tarball)" msgstr "설치 소스 (Tarball)" #: ../../content/administration/maintain/update.rst:108 msgid "" "If you have originally installed Odoo with the \"tarball\" version (source " "code archive), you have to replace the installation directory with a newer " "version. First download the latest tarball from Odoo.com. They are updated " "daily and include the latest security fixes (see step #1) After downloading " "the package, extract it to a temporary location on your server." msgstr "" "원래 \"Tarball\" 버전 (소스 코드 아카이브)으로 Odoo를 설치한 경우에는, 설치 디렉토리를 최신 버전으로 바꿔야 합니다. " "먼저 Odoo.com에서 최신 Tarball을 다운로드합니다. 업데이트는 매일 시행되며 최신 보안 수정 사항이 포함되어 있습니다 (1단계" " 참조). 패키지를 다운로드한 후 서버의 임시 위치에 압축을 풉니다." #: ../../content/administration/maintain/update.rst:113 msgid "" "You will get a folder labeled with the version of the source code, for " "example \"odoo-13.0+e.20190719\", that contains a folder \"odoo.egg-info\" " "and the actual source code folder named \"odoo\" (for Odoo 10 and later) or " "\"openerp\" for older versions. You can ignore the odoo.egg-info folder. " "Locate the folder where your current installation is deployed, and replace " "it with the newer \"odoo\" or \"openerp\" folder that was in the archive you" " just extracted." msgstr "" "소스 코드 버전이 표시된 폴더가 예를 들어, \"odoo-13.0+e.20190719\"와 같이 생성되며, \"odoo.egg-" "info\" 폴더와 \"odoo\" (Odoo 10 이상)라는 실제 소스 코드 폴더나 이전 버전의 경우 \"openerp\"라는 이름으로" " 폴더가 표시됩니다. odoo.egg-info 폴더는 무시해도 됩니다. 현재 설치 중인 내용이 배포된 폴더를 찾아 방금 압축을 푼 " "아카이브에 있는 최신 \"odoo\" 또는 \"openerp\" 폴더로 바꿉니다." #: ../../content/administration/maintain/update.rst:119 msgid "" "Be sure to match the folder layout, for example the new \"addons\" folder " "included in the source code should end up exactly at the same path it was " "before. Next, watch out for any specific configuration files that you may " "have manually copied or modified in the old folder, and copy them over to " "the new folder. Finally, restart the Odoo service or reboot the machine, and" " you are all set." msgstr "" "폴더 레이아웃이 일치하는지 확인합니다. 예를 들어 소스 코드에 포함된 새로운 \"addons\" 폴더는 이전과 동일한 경로에 있어야 " "합니다. 다음으로, 이전 폴더에서 직접 복사하거나 수정되었을 수 있는 특정 구성 파일을 찾아서 새 폴더에 복사합니다. 마지막으로 Odoo" " 서비스를 다시 시작하거나 컴퓨터를 재부팅하면 모든 설정이 완료됩니다." #: ../../content/administration/maintain/update.rst:126 msgid "Source Install (Github)" msgstr "" #: ../../content/administration/maintain/update.rst:128 msgid "" "If you have originally installed Odoo with a full Github clone of the " "official repositories, the update procedure requires you to pull the latest " "source code via git. Change into the directory for each repository (the main" " Odoo repository, and the Enterprise repository), and run the following " "commands::" msgstr "" #: ../../content/administration/maintain/update.rst:136 msgid "" "The last command may encounter source code conflicts if you had edited the " "Odoo source code locally. The error message will give you the list of files " "with conflicts, and you will need to resolve the conflicts manually, by " "editing them and deciding which part of the code to keep." msgstr "" #: ../../content/administration/maintain/update.rst:140 msgid "" "Alternatively, if you prefer to simply discard the conflicting changes and " "restore the official version, you can use the following command::" msgstr "" #: ../../content/administration/maintain/update.rst:145 msgid "" "Finally, restart the Odoo service or reboot the machine, and you should be " "done." msgstr "" #: ../../content/administration/maintain/update.rst:149 msgid "Docker" msgstr "" #: ../../content/administration/maintain/update.rst:151 msgid "" "Please refer to our `Docker image documentation " "`_ for specific update instructions." msgstr "" #: ../../content/administration/odoo_sh/advanced.rst:5 msgid "Advanced" msgstr "고급" #: ../../content/administration/odoo_sh/advanced/containers.rst:4 msgid "Containers" msgstr "" #: ../../content/administration/odoo_sh/advanced/containers.rst:7 #: ../../content/administration/odoo_sh/advanced/submodules.rst:9 #: ../../content/administration/odoo_sh/getting_started/branches.rst:6 #: ../../content/administration/odoo_sh/getting_started/builds.rst:9 #: ../../content/administration/odoo_sh/getting_started/first_module.rst:6 #: ../../content/administration/odoo_sh/getting_started/online-editor.rst:9 #: ../../content/administration/odoo_sh/getting_started/settings.rst:6 #: ../../content/administration/odoo_sh/getting_started/status.rst:6 #: ../../content/administration/odoo_sh/overview.rst:5 msgid "Overview" msgstr "입출고 현황" #: ../../content/administration/odoo_sh/advanced/containers.rst:9 msgid "" "Each build is isolated within its own container (Linux namespaced " "container)." msgstr "" #: ../../content/administration/odoo_sh/advanced/containers.rst:11 msgid "" "The base is an Ubuntu system, where all of Odoo's required dependencies, as " "well as common useful packages, are installed." msgstr "" #: ../../content/administration/odoo_sh/advanced/containers.rst:14 msgid "" "If your project requires additional Python dependencies, or more recent " "releases, you can define a :file:`requirements.txt` file in the root of your" " branches listing them. The platform will take care to install these " "dependencies in your containers. `The pip requirements specifiers " "`_ documentation can help you write a :file:`requirements.txt` " "file. To have a concrete example, check out the `requirements.txt file of " "Odoo `_." msgstr "" #: ../../content/administration/odoo_sh/advanced/containers.rst:22 msgid "" "The :file:`requirements.txt` files of submodules are taken into account as " "well. The platform looks for :file:`requirements.txt` files in each folder " "containing Odoo modules: Not in the module folder itself, but in their " "parent folder." msgstr "" #: ../../content/administration/odoo_sh/advanced/containers.rst:27 msgid "Directory structure" msgstr "" #: ../../content/administration/odoo_sh/advanced/containers.rst:29 msgid "" "As the containers are Ubuntu based, their directory structure follows the " "linux Filesystem Hierarchy Standard. `Ubuntu's filesystem tree overview " "`_" " explains the main directories." msgstr "" #: ../../content/administration/odoo_sh/advanced/containers.rst:33 msgid "Here are the Odoo.sh pertinent directories:" msgstr "" #: ../../content/administration/odoo_sh/advanced/containers.rst:73 msgid "Both Python 2.7 and 3.5 are installed in the containers. However:" msgstr "" #: ../../content/administration/odoo_sh/advanced/containers.rst:75 msgid "" "If your project is configured to use Odoo 10.0, the Odoo server runs with " "Python 2.7." msgstr "" #: ../../content/administration/odoo_sh/advanced/containers.rst:76 msgid "" "If your project is configured to use Odoo 11.0 or above, the Odoo server " "runs with Python 3.5." msgstr "" #: ../../content/administration/odoo_sh/advanced/containers.rst:79 msgid "Database shell" msgstr "" #: ../../content/administration/odoo_sh/advanced/containers.rst:81 msgid "" "While accessing a container with the shell, you can access the database " "using *psql*." msgstr "" #: ../../content/administration/odoo_sh/advanced/containers.rst:92 msgid "" "**Be careful !** `Use transactions " "`_ " "(*BEGIN...COMMIT/ROLLBACK*) for every *sql* statements leading to changes " "(*UPDATE*, *DELETE*, *ALTER*, ...), especially for your production database." msgstr "" #: ../../content/administration/odoo_sh/advanced/containers.rst:97 msgid "" "The transaction mechanism is your safety net in case of mistake. You simply " "have to rollback your changes to revert your database to its previous state." msgstr "" #: ../../content/administration/odoo_sh/advanced/containers.rst:100 msgid "" "For example, it may happen that you forget to set your *WHERE* condition." msgstr "" #: ../../content/administration/odoo_sh/advanced/containers.rst:111 msgid "" "In such a case, you can rollback to revert the unwanted changes that you " "just mistakenly did, and rewrite the statement:" msgstr "" #: ../../content/administration/odoo_sh/advanced/containers.rst:122 msgid "" "However, do not forget to either commit or rollback your transaction after " "having done it. Open transactions may lock records in your tables and your " "running database may wait for them to be released. It can cause a server to " "hang indefinitely." msgstr "" #: ../../content/administration/odoo_sh/advanced/containers.rst:126 msgid "" "In addition, when possible, use your staging databases to test your " "statements first. It gives you an extra safety net." msgstr "" #: ../../content/administration/odoo_sh/advanced/containers.rst:129 msgid "Run an Odoo server" msgstr "" #: ../../content/administration/odoo_sh/advanced/containers.rst:131 msgid "" "You can start an Odoo server instance from a container shell. You won't be " "able to access it from the outside world with a browser, but you can for " "instance:" msgstr "" #: ../../content/administration/odoo_sh/advanced/containers.rst:134 msgid "use the Odoo shell," msgstr "" #: ../../content/administration/odoo_sh/advanced/containers.rst:146 msgid "install a module," msgstr "" #: ../../content/administration/odoo_sh/advanced/containers.rst:152 msgid "update a module," msgstr "" #: ../../content/administration/odoo_sh/advanced/containers.rst:158 msgid "run the tests for a module," msgstr "" #: ../../content/administration/odoo_sh/advanced/containers.rst:164 msgid "In the above commands, the argument:" msgstr "" #: ../../content/administration/odoo_sh/advanced/containers.rst:166 msgid "``--without-demo=all`` prevents demo data to be loaded for all modules" msgstr "" #: ../../content/administration/odoo_sh/advanced/containers.rst:167 msgid "" "``--stop-after-init`` will immediately shutdown the server instance after it" " completed the operations you asked." msgstr "" #: ../../content/administration/odoo_sh/advanced/containers.rst:169 msgid "" "More options are available and detailed in the :doc:`CLI documentation " "`." msgstr "" #: ../../content/administration/odoo_sh/advanced/containers.rst:172 msgid "" "You can find in the logs (*~/logs/odoo.log*) the addons path used by Odoo.sh" " to run your server. Look for \"*odoo: addons paths*\":" msgstr "" #: ../../content/administration/odoo_sh/advanced/containers.rst:181 msgid "" "**Be careful**, especially with your production database. Operations that " "you perform running this Odoo server instance are not isolated: Changes will" " be effective in the database. Always, make your tests in your staging " "databases." msgstr "" #: ../../content/administration/odoo_sh/advanced/containers.rst:186 msgid "Debugging in Odoo.sh" msgstr "" #: ../../content/administration/odoo_sh/advanced/containers.rst:188 msgid "" "Debugging an Odoo.sh build is not really different than another Python app. " "This article only explains the specificities and limitations of the Odoo.sh " "platform, and assumes that you already know how to use a debugger." msgstr "" #: ../../content/administration/odoo_sh/advanced/containers.rst:190 msgid "" "If you don't know how to debug a Python application yet, there are multiple " "introductory courses that can be easily found on the Internet." msgstr "" #: ../../content/administration/odoo_sh/advanced/containers.rst:192 msgid "" "You can use ``pdb``, ``pudb`` or ``ipdb`` to debug your code on Odoo.sh. As " "the server is run outside a shell, you cannot launch the debugger directly " "from your Odoo instance backend as the debugger needs a shell to operate." msgstr "" #: ../../content/administration/odoo_sh/advanced/containers.rst:195 msgid "" "`pdb `_ is installed by default " "in every container." msgstr "" #: ../../content/administration/odoo_sh/advanced/containers.rst:197 msgid "" "If you want to use `pudb `_ or `ipdb " "`_ you have to install it before." msgstr "" #: ../../content/administration/odoo_sh/advanced/containers.rst:199 msgid "To do so, you have two options:" msgstr "" #: ../../content/administration/odoo_sh/advanced/containers.rst:201 msgid "temporary (only in the current build):" msgstr "" #: ../../content/administration/odoo_sh/advanced/containers.rst:207 msgid "or" msgstr "또는" #: ../../content/administration/odoo_sh/advanced/containers.rst:213 msgid "" "permanent: add ``pudb`` or ``ipdb`` to your project ``requirements.txt`` " "file." msgstr "" #: ../../content/administration/odoo_sh/advanced/containers.rst:216 msgid "" "Then edit the code where you want to trigger the debugger and add this:" msgstr "" #: ../../content/administration/odoo_sh/advanced/containers.rst:224 msgid "" "The condition :code:`sys.__stdin__.isatty()` is a hack that detects if you " "run Odoo from a shell." msgstr "" #: ../../content/administration/odoo_sh/advanced/containers.rst:226 msgid "Save the file and then run the Odoo Shell:" msgstr "" #: ../../content/administration/odoo_sh/advanced/containers.rst:232 msgid "" "Finally, *via* the Odoo Shell, you can trigger the piece of " "code/function/method you want to debug." msgstr "" #: ../../content/administration/odoo_sh/advanced/containers.rst-1 msgid "Console screenshot showing ``pdb`` running in an Odoo.sh shell." msgstr "" #: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:6 msgid "Frequent Technical Questions" msgstr "" #: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:9 msgid "\"Scheduled actions do not run at the exact time they were expected\"" msgstr "" #: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:11 msgid "" "On the Odoo.sh platform, we cannot guarantee an exact running time for " "scheduled actions." msgstr "" #: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:13 msgid "" "This is due to the fact that there might be multiple customers on the same " "server, and we must guarantee a fair share of the server for every customer." " Scheduled actions are therefore implemented slightly differently than on a " "regular Odoo server, and are run on a *best effort* policy." msgstr "" #: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:16 msgid "" "Do not expect any scheduled action to be run more often than every 5 min." msgstr "" #: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:19 msgid "Are there \"best practices\" regarding scheduled actions?" msgstr "" #: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:21 msgid "" "**Odoo.sh always limits the execution time of scheduled actions (*aka* " "crons).** Therefore, you must keep this fact in mind when developing your " "own crons." msgstr "" #: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:24 msgid "We advise that:" msgstr "" #: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:26 msgid "Your scheduled actions should work on small batches of records." msgstr "" #: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:27 msgid "" "Your scheduled actions should commit their work after processing each batch;" " this way, if they get interrupted by the time-limit, there is no need to " "start over." msgstr "" #: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:29 msgid "" "Your scheduled actions should be `idempotent " "`_: they must not cause side-" "effects if they are started more often than expected." msgstr "" #: ../../content/administration/odoo_sh/advanced/submodules.rst:6 #: ../../content/administration/odoo_sh/getting_started/settings.rst:170 msgid "Submodules" msgstr "" #: ../../content/administration/odoo_sh/advanced/submodules.rst:11 msgid "" "A `Git submodule `_ " "allows you to integrate other Git projects into your code, without the need " "to copy-paste all their code." msgstr "" #: ../../content/administration/odoo_sh/advanced/submodules.rst:14 msgid "" "Indeed, your custom modules can depend on modules from other repositories. " "Regarding Odoo, this feature allows you to add modules from other Git " "repositories into the branches of your repository. Adding these dependencies" " in your branch through submodules makes the deployment of your code and " "servers easier, as you can clone the repositories added as submodules at the" " same time you clone your own repository." msgstr "" #: ../../content/administration/odoo_sh/advanced/submodules.rst:19 msgid "" "Besides, you can choose the branch of the repository added as submodule and " "you have the control of the revision you want. It's up to you to decide " "whether you want to pin the submodule to a specific revision and when you " "want to update to a newer revision." msgstr "" #: ../../content/administration/odoo_sh/advanced/submodules.rst:24 msgid "" "In Odoo.sh, the submodules give you the possibility to use and depend on " "modules available in other repositories. The platform will detect that you " "added modules through submodules in your branches and add them to your " "addons path automatically so you can install them in your databases." msgstr "" #: ../../content/administration/odoo_sh/advanced/submodules.rst:28 msgid "" "If you add private repositories as submodules in your branches, you need to " "configure a deploy key in your Odoo.sh project settings and in your " "repository settings. Otherwise Odoo.sh won't be allowed to download them. " "The procedure is detailed in the chapter :ref:`Settings > Submodules " "`." msgstr "" #: ../../content/administration/odoo_sh/advanced/submodules.rst:34 msgid "Adding a submodule" msgstr "" #: ../../content/administration/odoo_sh/advanced/submodules.rst:37 msgid "With Odoo.sh (simple)" msgstr "" #: ../../content/administration/odoo_sh/advanced/submodules.rst:40 msgid "" "For now it is not possible to add **private** repositories with this method." " You can nevertheless do so :ref:`with Git `." msgstr "" #: ../../content/administration/odoo_sh/advanced/submodules.rst:43 msgid "" "On Odoo.sh, in the branches view of your project, choose the branch in which" " you want to add a submodule." msgstr "" #: ../../content/administration/odoo_sh/advanced/submodules.rst:45 msgid "" "In the upper right corner, click on the *Submodule* button, and then on " "*Run*." msgstr "" #: ../../content/administration/odoo_sh/advanced/submodules.rst:50 msgid "A dialog with a form is shown. Fill the inputs as follows:" msgstr "" #: ../../content/administration/odoo_sh/advanced/submodules.rst:52 msgid "Repository URL: The SSH URL of the repository." msgstr "" #: ../../content/administration/odoo_sh/advanced/submodules.rst:53 msgid "Branch: The branch you want to use." msgstr "" #: ../../content/administration/odoo_sh/advanced/submodules.rst:54 msgid "" "Path: The folder in which you want to add this submodule in your branch." msgstr "" #: ../../content/administration/odoo_sh/advanced/submodules.rst:59 msgid "" "On Github, you can get the repository URL with the *Clone or download* " "button of the repository. Make sure to *use SSH*." msgstr "" #: ../../content/administration/odoo_sh/advanced/submodules.rst:67 msgid "With Git (advanced)" msgstr "" #: ../../content/administration/odoo_sh/advanced/submodules.rst:69 msgid "" "In a terminal, in the folder where your Git repository is cloned, checkout " "the branch in which you want to add a submodule:" msgstr "" #: ../../content/administration/odoo_sh/advanced/submodules.rst:76 msgid "Then, add the submodule using the command below:" msgstr "" #: ../../content/administration/odoo_sh/advanced/submodules.rst:82 #: ../../content/administration/odoo_sh/advanced/submodules.rst:94 #: ../../content/administration/odoo_sh/getting_started/first_module.rst:360 #: ../../content/administration/odoo_sh/getting_started/first_module.rst:498 msgid "Replace" msgstr "대체" #: ../../content/administration/odoo_sh/advanced/submodules.rst:84 msgid "" "*:* by the SSH URL of the " "repository you want to add as submodule," msgstr "" #: ../../content/administration/odoo_sh/advanced/submodules.rst:85 msgid "** by the branch you want to use in the above repository," msgstr "" #: ../../content/administration/odoo_sh/advanced/submodules.rst:86 msgid "** by the folder in which you want to add this submodule." msgstr "" #: ../../content/administration/odoo_sh/advanced/submodules.rst:88 msgid "Commit and push your changes:" msgstr "" #: ../../content/administration/odoo_sh/advanced/submodules.rst:96 msgid "" " by the repository on which you want to push your changes. For a " "standard Git setup, this is *origin*." msgstr "" #: ../../content/administration/odoo_sh/advanced/submodules.rst:97 msgid "" " by the branch on which you want to push your changes. Most likely " "the branch you used :code:`git checkout` on in the first step." msgstr "" #: ../../content/administration/odoo_sh/advanced/submodules.rst:100 msgid "" "You can read the `git-scm.com documentation `_ for more details about the Git " "submodules. For instance, if you would like to update your submodules to " "have their latest revision, you can follow the chapter `Pulling in Upstream " "changes `_." msgstr "" #: ../../content/administration/odoo_sh/advanced/submodules.rst:107 msgid "Ignore modules" msgstr "" #: ../../content/administration/odoo_sh/advanced/submodules.rst:109 msgid "" "If you're adding a repository that contains a lot of modules, you may want " "to ignore some of them in case there are any that are installed " "automatically. To do so, you can prefix your submodule folder with a " ":code:`.`. The platform will ignore this folder and you can hand pick your " "modules by creating symlinks to them from another folder." msgstr "" #: ../../content/administration/odoo_sh/getting_started.rst:5 msgid "Get started" msgstr "시작함" #: ../../content/administration/odoo_sh/getting_started/branches.rst:3 msgid "Branches" msgstr "지점" #: ../../content/administration/odoo_sh/getting_started/branches.rst:8 msgid "" "The branches view gives you an overview of the different branches your " "repository has." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:16 #: ../../content/administration/odoo_sh/getting_started/builds.rst:41 msgid "Stages" msgstr "단계" #: ../../content/administration/odoo_sh/getting_started/branches.rst:18 msgid "" "Odoo.sh offers three different stages for your branches: production, staging" " and development." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:20 msgid "" "You can change the stage of a branch by drag and dropping it into the stage " "section title." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:28 #: ../../content/administration/odoo_sh/getting_started/builds.rst:44 msgid "Production" msgstr "생산" #: ../../content/administration/odoo_sh/getting_started/branches.rst:30 msgid "" "This is the branch holding the code on which your production database runs. " "There can be only one production branch." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:33 msgid "" "When you push a new commit in this branch, your production server is updated" " with the code of the new revision and is then restarted." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:36 msgid "" "If your changes require the update of a module, such as a change in a form " "view, and you want it to be performed automatically, increase the version " "number of the module in its manifest (*__manifest__.py*). The platform will " "then take care to perform the update during which the instance will be held " "temporarily unavailable for maintenance reason." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:43 msgid "" "This method is equivalent to perform an upgrade of the module through the " "Apps menu, or through the :code:`-u` switch of :doc:`the command line " "`." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:47 msgid "" "In the case the changes in the commit prevent the server to restart, or if " "the modules update fails, the server is automatically reverted to the " "previous successful code revision and the database is roll-backed as it was " "before the update. You still have access to the log of the failed update, so" " you can troubleshoot it." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:53 msgid "" "The demo data is not loaded, as it is not meant to be used in a production " "database. The unit tests are not performed, as it would increase the " "unavailability time of the production database during the updates." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:57 msgid "" "Partners using trial projects should be aware their production branch, along" " with all the staging branches, will automatically be set back to the " "development stage after 30 days." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:61 #: ../../content/administration/odoo_sh/getting_started/builds.rst:63 msgid "Staging" msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:63 msgid "" "Staging branches are meant to test your new features using the production " "data without compromising the actual production database with test records. " "They will create databases that are neutralized duplicates of the production" " database." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:67 msgid "The neutralization includes:" msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:69 msgid "" "Disabling scheduled actions. If you want to test them, you can trigger their" " action manually or re-enable them. Be aware that the platform will trigger " "them less often if no one is using the database in order to save up " "resources." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:72 msgid "" "Disabling outgoing emails by intercepting them with a mailcatcher. An " ":ref:`interface to view ` the " "emails sent by your database is provided. That way, you do not have to worry" " about sending test emails to your contacts." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:75 msgid "Setting payment providers and shipping providers in test mode." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:76 msgid "Disabling IAP services" msgstr "IAP 서비스 비활성화하기" #: ../../content/administration/odoo_sh/getting_started/branches.rst:78 msgid "" "The latest database will be kept alive indefinitely, older ones from the " "same branch may get garbage collected to make room for new ones. It will be " "valid for 3 months, after which you will be expected to rebuild the branch. " "If you make configuration or view changes in these databases, make sure to " "document them or write them directly in the modules of the branch, using XML" " data files overriding the default configuration or views." msgstr "" "가장 최근의 데이터베이스는 무기한 보존되며, 같은 브랜치의 오래된 데이터베이스는 새 데이터베이스를 위한 공간을 확보하기 위해 가비지 " "컬렉션될 수 있습니다. 이러한 데이터베이스는 3개월 동안 유효하며, 그 이후에는 브랜치를 다시 빌드해야 합니다. 이러한 데이터베이스에서 " "구성 또는 보기 변경을 구현하는 경우 이를 문서화하거나 XML 데이터 파일을 사용하여 브랜치의 모듈에 직접 삽입하여 기본 구성 또는 " "보기를 재정의하는 것이 중요합니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:83 msgid "" "The unit tests are not performed as, in Odoo, they currently rely on the " "demo data, which is not loaded in the production database. In the future, if" " Odoo supports to run the unit tests without the demo data, Odoo.sh will " "then consider running the tests on staging databases." msgstr "" "Odoo에서 단위 테스트는, 현재 프로덕션 데이터베이스에 로드가 되지 않은 데모 데이터에 의존하기 때문에 실행되지 않습니다. 앞으로 " "Odoo가 데모 데이터 없이 단위 테스트가 실행되도록 지원한다면 Odoo.sh는 스테이징 데이터베이스에서 테스트를 실행하는 것을 " "고려하겠습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:88 #: ../../content/administration/odoo_sh/getting_started/builds.rst:81 #: ../../content/administration/odoo_sh/getting_started/settings.rst:56 msgid "Development" msgstr "개발" #: ../../content/administration/odoo_sh/getting_started/branches.rst:90 msgid "" "Development branches create new databases using the demo data to run the " "unit tests. The installed modules are the ones included in your branches. " "You can change this list of modules to install in your :ref:`project " "Settings `." msgstr "" "개발 브랜치에서는 데모 데이터로 새 데이터베이스를 생성하여 단위 테스트를 실행합니다. 설치된 모듈은 브랜치에 있는 모듈입니다. " ":ref:`프로젝트 설정 `.에서 설치할 " "모듈 목록을 변경할 수 있습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:94 msgid "" "When you push a new commit in one of these branches, a new server is " "started, with a database created from scratch and the new revision of the " "branch. The demo data is loaded, and the unit tests are performed by " "default. This verifies your changes do not break any of the features tested " "by them. If you wish, you can disable the tests or allow specific tests to " "be run with custom tags in the :ref:`branch's settings `." msgstr "" "이와 같은 브랜치 중 하나에 새 커밋을 푸시하면 처음부터 새로 생성되고 브랜치가 변경되어 새 서버가 시작됩니다. 데모 데이터를 블러와서 " "기본값으로 단위 테스트가 수행됩니다. 이를 통해 변경 사항 때문에 테스트한 기능이 손상되지 않았는지 확인합니다. 원하는 경우 테스트를 " "비활성화하거나 :ref:`브랜치 설정 `에서 사용자 " "정의 태그를 사용하여 특정 테스트가 실행되도록 허용할 수 있습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:101 msgid "" "Similar to staging branches, the emails are not sent but are intercepted by " "a mailcatcher and scheduled actions are not triggered as long as the " "database is not in use." msgstr "" "스테이징 브랜치와 마찬가지로 이메일은 전송되지 않지만 메일 캐처를 이용하여 차단되고 데이터베이스가 사용 중인 경우가 아니면 예약된 작업은" " 트리거되지 않습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:104 msgid "" "The databases created for development branches are meant to live around " "three days. After that, they can be automatically garbage collected to make " "room for new databases without prior notice." msgstr "" "개발 브랜치용으로 생성된 데이터베이스는 약 3일 정도 사용할 수 있습니다. 그 후에는 새 데이터베이스를 위한 공간을 확보하기 위해 사전 " "안내 없이 자동으로 휴지통으로 이동될 수 있습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:110 msgid "Merging your branches" msgstr "브랜치 병합하기" #: ../../content/administration/odoo_sh/getting_started/branches.rst:112 msgid "" "You can merge your branches easily by drag and dropping them into each " "other." msgstr "브랜치를 서로 끌어다 놓는 방식으로 쉽게 병합할 수 있습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:117 msgid "" "When you want to test the changes of your development branches with the " "production data, you can either:" msgstr "프로덕션 데이터를 사용하여 개발 브랜치의 변경 사항을 테스트하려는 경우 다음 중 선택할 수 있습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:120 msgid "" "merge the development branch into your staging branch, by drag and dropping " "it onto the desired staging branch," msgstr "개발 브랜치를 원하는 스테이징 브랜치에 끌어다 놓고 스테이징 브랜치에 병합합니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:121 msgid "" "drag and dropping the development branch on the staging section title, to " "make it become a staging branch." msgstr "개발 브랜치를 스테이징 섹션 제목에 끌어다 놓아서 스테이징 브랜치가 되도록 합니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:123 msgid "" "When your latest changes are ready for production, you can drag and drop " "your staging branch onto your production branch to merge and deploy in " "production your newest features." msgstr "" "최근 변경한 내용을 프로덕션에 적용할 준비가 끝나면, 스테이징 브랜치를 프로덕션 브랜치로 끌어다 놓아서 최신 기능을 프로덕션에 병합하고 " "배포할 수 있게 합니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:127 msgid "" "If you are bold enough, you can merge your development branches into your " "production branch as well. It just means you skip the validation of your " "changes with the production data through a staging branch." msgstr "" "과감하게 개발 브랜치를 프로덕션 브랜치에 병합할 수도 있습니다. 이는 스테이징 브랜치로 프로덕션 데이터에 대한 변경 사항 승인을 " "생략한다는 의미에 불과합니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:131 msgid "" "You can merge your development branches into each other, and your staging " "branches into each other." msgstr "개발 브랜치를 서로, 또한 스테이징 브랜치를 서로 병합할 수 있습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:133 msgid "" "Of course, you can also use :code:`git merge` directly on your workstation " "to merge your branches. Odoo.sh will be notified when new revisions have " "been pushed in your branches." msgstr "" "물론 워크스테이션에서 직접 :code:`git merge`를 사용하여 브랜치를 병합할 수도 있습니다. 브랜치에 새로운 개정 사항이 " "푸시되면 Odoo.sh에서 알림을 받게 됩니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:136 msgid "" "Merging a staging branch in the production branch only merges the source " "code: Any configuration changes you made in the staging databases are not " "passed to the production database." msgstr "" "프로덕션 브랜치에 스테이징 브랜치를 병합하는 경우 소스 코드만 병합됩니다. 스테이징 데이터베이스에서 변경한 설정 내용은 프로덕션 " "데이터베이스로 이전되지 않습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:139 msgid "" "If you test configuration changes in staging branches, and want them to be " "applied in the production, you have to either:" msgstr "스테이징 브랜치에서 환경 설정에서 변경한 사항을 테스트하고 프로덕션에 적용하려면 다음 중에서 선택하여 진행해야 합니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:141 msgid "" "write the configuration changes in XML data files overriding the default " "configuration or views in your branches, and then increase the version of " "your module in its manifest (*__manifest__.py*) to trigger the update of the" " module when you merge your staging branch in your production branch. This " "is the best practice for a better scalability of your developments as you " "will use the Git versioning features for all your configuration changes, and" " therefore have a traceability for your changes." msgstr "" "브랜치의 기본 환경 설정이나 기본 화면을 재지정하도록 XML 데이터 파일에 설정 변경 사항을 기재한 다음 매니페스트 " "(*__manifest__.py*)에서 모듈 버전을 높여서 스테이징 브랜치를 병합할 때 모듈 업데이트가 트리거되도록 합니다. 이는 설정 " "변경에 Git 버전 관리 기능을 사용하여 변경 사항을 추적할 수 있으므로 개발 확장성을 향상시키는 데 가장 좋은 방법입니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:147 msgid "" "pass them manually from your staging to your production database, by " "copy/pasting them." msgstr "스테이징에서 프로덕션 데이터베이스로 복사/붙여넣기를 통해 직접 이전합니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:152 msgid "Tabs" msgstr "탭" #: ../../content/administration/odoo_sh/getting_started/branches.rst:155 #: ../../content/administration/odoo_sh/getting_started/settings.rst:57 #: ../../content/administration/odoo_sh/getting_started/settings.rst:85 msgid "History" msgstr "기록" #: ../../content/administration/odoo_sh/getting_started/branches.rst:157 msgid "An overview of your branch history:" msgstr "브랜치 이력에 대한 개요:" #: ../../content/administration/odoo_sh/getting_started/branches.rst:159 msgid "The messages of the commits and their authors," msgstr "커밋 및 커밋 작성자 메시지," #: ../../content/administration/odoo_sh/getting_started/branches.rst:160 msgid "" "The various events linked to the platform, such as stage changes, database " "imports, backup restores." msgstr "스테이지 변경이나 데이터베이스 가져오기, 백업 복원 등 플랫폼과 연결된 다양한 이벤트입니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:165 msgid "" "For each event, a status is displayed in the top right-hand corner. It can " "provide information about the ongoing operation on the database " "(installation, update, backup import, ...), or its result (tests feedback, " "successful backup import, ...). When an operation is successful, you can " "access the database thanks to the *connect* button." msgstr "" "각 이벤트의 상태는 오른쪽 상단 모서리에 표시됩니다. 데이터베이스에서 진행 중인 작업 (설치, 업데이트, 백업 가져오기 등)이나 해당 " "결과 (테스트 피드백, 백업 가져오기 성공 등)에 대한 정보를 확인할 수 있습니다. 작업이 성공하면 *연결* 버튼을 누르면 데이터베이스에" " 액세스할 수 있습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:173 #: ../../content/administration/odoo_sh/getting_started/settings.rst:73 #: ../../content/administration/odoo_sh/getting_started/settings.rst:101 msgid "Mails" msgstr "메일" #: ../../content/administration/odoo_sh/getting_started/branches.rst:175 msgid "" "This tab contains the mail catcher. It displays an overview of the emails " "sent by your database. The mail catcher is available for your development " "and staging branches as the emails of your production database are really " "sent instead of being intercepted." msgstr "" "이 탭에는 메일 수집기가 포함되어 있습니다. 여기에서 데이터베이스에서 전송된 이메일에 대한 전반적인 내용을 확인할 수 있습니다. 메일 " "수집기는 개발 및 준비 브랜치에서 사용할 수 있으며 .프로덕션 데이터베이스의 이메일이 남겨져 있는 대신 실제로 전송될 수 있게 됩니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:184 msgid "Shell" msgstr "셸" #: ../../content/administration/odoo_sh/getting_started/branches.rst:186 msgid "" "A shell access to your container. You can perform basic linux commands " "(:code:`ls`, :code:`top`) and open a shell on your database by typing " ":code:`psql`." msgstr "" "컨테이너에 대한 셸 액세스입니다. 기본 Linux 명령어 (:code:`ls`, :code:`top`)로 진행하고 " ":code:`psql`을 입력하면 데이터베이스에서 셸을 열 수 있습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:192 #: ../../content/administration/odoo_sh/getting_started/branches.rst:208 msgid "" "You can open multiple tabs and drag-and-drop them to arrange the layout as " "you wish, for instance side by side." msgstr "" "탭을 여러 개 열고 드래그 앤 드롭 기능을 통해 원하는 대로 레이아웃을 정렬할 수 있습니다. 예를 들어, 나란히 배치해 보세요." #: ../../content/administration/odoo_sh/getting_started/branches.rst:196 msgid "" "Long running shell instances are not guaranteed. Idle shells can be " "disconnected at anytime in order to free up resources." msgstr "셸 인스턴스는 장기적으로 실행되도록 보장되지 않습니다. 유휴 셸은 리소스를 확보하기 위해 언제든지 연결을 끊을 수 있습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:200 msgid "Editor" msgstr "편집가" #: ../../content/administration/odoo_sh/getting_started/branches.rst:202 msgid "" "An online integrated development environment (IDE) to edit the source code. " "You can also open terminals, Python consoles and even Odoo Shell consoles." msgstr "" "소스 코드를 편집할 수 있는 온라인 통합 개발 환경 (IDE)입니다. 터미널, Python 콘솔 및 Odoo 셸 콘솔까지 열 수 " "있습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:212 #: ../../content/administration/odoo_sh/getting_started/settings.rst:105 msgid "Monitoring" msgstr "모니터링" #: ../../content/administration/odoo_sh/getting_started/branches.rst:214 msgid "This link contains various monitoring metrics of the current build." msgstr "이 링크에는 현재의 빌드에 대한 다양한 모니터링 측정 항목이 있습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:219 msgid "" "You can zoom, change the time range or select a specific metric on each " "graph. On the graphs, annotations help you relate to changes on the build " "(database import, git push, etc...)." msgstr "" "각 그래프에서 확대/축소하거나, 시간 범위를 변경할 수 있으며, 특정한 측정 항목을 선택할 수 있습니다. 그래프에서 주석으로 빌드 변경 " "사항 (데이터베이스 가져오기, git push 등)과 관련된 정보를 안내할 수 있습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:225 #: ../../content/administration/odoo_sh/getting_started/settings.rst:65 #: ../../content/administration/odoo_sh/getting_started/settings.rst:93 msgid "Logs" msgstr "로그" #: ../../content/administration/odoo_sh/getting_started/branches.rst:227 msgid "A viewer to have a look to your server logs." msgstr "뷰어로 서버 로그를 살펴볼 수 있습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:232 msgid "Different logs are available:" msgstr "다양한 로그를 사용할 수 있습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:234 msgid "" "install.log: The logs of the database installation. In a development branch," " the logs of the tests are included." msgstr "install.log: 데이터베이스 설치 로그입니다. 개발 브랜치에는 테스트 로그가 포함되어 있습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:235 msgid "pip.log: The logs of the Python dependencies installation." msgstr "pip.log: Python 종속성 설치 로그입니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:236 msgid "odoo.log: The logs of the running server." msgstr "odoo.log: 실행 중인 서버의 로그입니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:237 msgid "update.log: The logs of the database updates." msgstr "update.log: 데이터베이스 업데이트 로그입니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:238 msgid "" "pg_long_queries.log: The logs of psql queries that take an unusual amount of" " time." msgstr "pg_long_queries.log: 소요 시간이 비정상적인 psql 쿼리의 로그입니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:240 msgid "" "If new lines are added in the logs, they will be displayed automatically. If" " you scroll to the bottom, the browser will scroll automatically each time a" " new line is added." msgstr "" "로그에 새로운 줄이 추가되면 자동으로 표시됩니다. 맨 아래로 스크롤을 이동하면 새 줄이 추가될 때마다 브라우저가 자동으로 스크롤이 " "이동됩니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:243 msgid "" "You can pause the logs fetching by clicking on the according button in the " "upper right corner of the view. The fetching is automatically stopped after " "5 minutes. You can restart it using the play button." msgstr "" "화면에서 오른쪽 상단에 있는 해당 버튼을 클릭하면 로그 가져오기를 일시 중지할 수 있습니다. 로그 가져오기는 5분 후에 자동으로 " "중지됩니다. 재생 버튼을 사용하여 다시 시작할 수 있습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:249 #: ../../content/administration/odoo_sh/getting_started/settings.rst:109 msgid "Backups" msgstr "백업" #: ../../content/administration/odoo_sh/getting_started/branches.rst:251 msgid "" "A list of the backups available for download and restore, the ability to " "perform a manual backup and to import a database." msgstr "다운로드 및 복원할 수 있는 백업 목록, 수동 백업 수행 및 데이터베이스 가져오기 기능입니다" #: ../../content/administration/odoo_sh/getting_started/branches.rst:257 msgid "" "Odoo.sh makes daily backups of the production database. It keeps 7 daily, 4 " "weekly and 3 monthly backups. Each backup includes the database dump, the " "filestore (attachments, binary fields), logs and sessions." msgstr "" "Odoo.sh에서는 프로덕션 데이터베이스가 매일 백업됩니다. 매일 7회, 매주 4회, 매월 3회 백업이 진행됩니다. 백업에는 데이터베이스" " 덤프, 파일 저장소(첨부 파일, 바이너리 필드), 로그 및 세션을 포함하여 백업됩니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:260 msgid "" "Staging and development databases are not backed up. You nevertheless have " "the possibility to restore a backup of the production database in your " "staging branches, for testing purposes, or to manually recover data that has" " been deleted by accident from the production database." msgstr "" "스테이징 및 개발 데이터베이스는 백업되지 않습니다. 다만 스테이징 브랜치에서 테스트 목적으로 프로덕션 데이터베이스의 백업을 복원하거나 " "프로덕션 데이터베이스에서 실수로 삭제된 데이터는 수기로 복구할 수 있습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:264 msgid "" "The list contains the backups kept on the server your production database is" " hosted on. This server only keeps one month of backups: 7 daily and 4 " "weekly backups." msgstr "" "이 목록에는 프로덕션 데이터베이스가 호스팅되는 서버에 보관된 백업이 포함되어 있습니다. 서버에는 한 달 분량의 백업으로 일일 7회 백업," " 주간 4회 백업만 보관됩니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:267 msgid "" "Dedicated backup servers keep the same backups, as well as 3 additional " "monthly backups. To restore or download one of these monthly backups, please" " `contact us `_." msgstr "" "전용 백업 서버는 백업을 동일하게 진행하되 월간 3회를 추가로 백업합니다. 월별 백업 중 하나를 복원하거나 다운로드하려면 `문의하기 " "`_로 연락주시기 바랍니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:270 msgid "" "If you merge a commit updating the version of one or several modules (in " ":file:`__manifest__.py`), or their linked python dependencies (in " ":file:`requirements.txt`), then Odoo.sh performs a backup automatically " "(flagged with type Update in the list), as either the container will be " "changed by the installation of new pip packages, either the database itself " "will be changed with the module update triggered afterwards. In these two " "cases, we are doing a backup as it may potentially break things." msgstr "" "하나 또는 여러 모듈 (:file:`__manifest__.py`) 또는 관련 Python 종속성 " "(:file:`requirements.txt`)의 버전을 업데이트하는 커밋을 병합하면 Odoo.sh는 자동으로 백업을 시작합니다. " "(목록에 업데이트 유형으로 표시) 이는 새 pip 패키지를 설치하여 컨테이너가 변경되거나 후속 모듈 업데이트를 통해 데이터베이스 자체가 " "변경될 수 있으므로 필요합니다. 두 가지 경우 모두 문제 발생의 잠재적 위험을 완화하기 위해 백업을 수행하는 것이 필수적입니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:276 msgid "" "If you merge a commit that only changes some code without the above-" "mentioned modifications, then no backup is done by Odoo.sh, as neither the " "container nor the database is modified so the platform considers this safe " "enough. Of course, as an extra precaution, you can make a backup manually " "before making big changes in your production sources in case something goes " "wrong (those manual backups are available for about one week). To avoid " "abuse, we limit manual backups to 5 per day." msgstr "" "앞서 언급한 수정 없이 코드만 변경하는 커밋을 병합하는 경우, Odoo.sh는 백업을 수행하지 않습니다. 이는 컨테이너나 데이터베이스가 " "수정되지 않아 플랫폼이 충분히 안전하다고 판단하기 때문입니다. 추가적인 예방 조치로, 예상치 못한 문제가 발생할 경우를 대비하여 프로덕션" " 소스에 중요한 변경 사항을 적용하기 전에 수동으로 백업을 생성할 수 있습니다. (이러한 수동 백업은 약 1주일 동안 액세스할 수 있음)" " 오용을 방지하기 위해 수동 백업은 하루에 5개로 제한합니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:282 msgid "" "The *import database* feature accepts database archives in the format " "provided by:" msgstr "*데이터베이스 가져오기* 기능은 다음 형식으로 데이터베이스에 보관할 수 있습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:284 msgid "" "the standard Odoo databases manager, (available for on-premise Odoo servers " "under :code:`/web/database/manager`)" msgstr "" "표준 Odoo 데이터베이스 관리자 (:code:`/web/database/manager` 아래에 있는 Odoo 온프레미스 서버에서 사용 " "가능)" #: ../../content/administration/odoo_sh/getting_started/branches.rst:286 msgid "the Odoo online databases manager," msgstr "Odoo 온라인 데이터베이스 관리자," #: ../../content/administration/odoo_sh/getting_started/branches.rst:287 msgid "the Odoo.sh backup download button of this *Backups* tab," msgstr "이 *백업* 탭에 있는 Odoo.sh 백업 다운로드 버튼," #: ../../content/administration/odoo_sh/getting_started/branches.rst:288 msgid "" "the Odoo.sh dump download button in the :ref:`Builds view `." msgstr ":ref:`빌드 화면 `에 있는 Odoo.sh 덤프 다운로드 버튼." #: ../../content/administration/odoo_sh/getting_started/branches.rst:295 msgid "Available for production and staging branches for valid projects." msgstr "유효한 프로젝트에서 프로덕션 및 스테이징 브랜치에 사용할 수 있습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:298 msgid ":doc:`Upgrade documentation <../../upgrade>`" msgstr ":doc:`업그레이드 문서 <../../upgrade>`" #: ../../content/administration/odoo_sh/getting_started/branches.rst:303 #: ../../content/administration/odoo_sh/getting_started/settings.rst:3 #: ../../content/administration/odoo_sh/getting_started/settings.rst:81 #: ../../content/administration/odoo_sh/getting_started/settings.rst:117 #: ../../content/administration/odoo_sh/getting_started/settings.rst:124 msgid "Settings" msgstr "설정" #: ../../content/administration/odoo_sh/getting_started/branches.rst:305 msgid "" "Here you can find a couple of settings that only apply to the currently " "selected branch." msgstr "여기에는 현재 선택한 브랜치에만 적용되는 설정이 몇 가지 있습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:310 msgid "**Behaviour upon new commit**" msgstr "**새로운 커밋에 대한 동작**" #: ../../content/administration/odoo_sh/getting_started/branches.rst:312 msgid "" "For development and staging branches, you can change the branch's behavior " "upon receiving a new commit. By default, a development branch will create a " "new build and a staging branch will update the previous build (see the " ":ref:`Production Stage `). This is especially useful " "should the feature you're working on require a particular setup or " "configuration, to avoid having to manually set it up again on every commit. " "If you choose new build for a staging branch, it will make a fresh copy from" " the production build every time a commit is pushed. A branch that is put " "back from staging to development will automatically be set to 'Do nothing'." msgstr "" "개발 브랜치 및 스테이징 브랜치의 경우 새로운 커밋을 받으면 브랜치의 동작을 변경할 수 있습니다. 기본적으로, 개발 브랜치는 새 빌드를 " "생성하고 스테이징 브랜치는 이전 빌드를 업데이트합니다 (:ref:`프로덕션 단계 ` 참조). 이 기능은 " "작업 중인 기능에 특정한 설정이나 환경 설정이 필요한 경우 커밋할 때마다 직접 다시 설정할 필요가 없으므로 특히 유용합니다. 스테이징 " "브랜치에 새 빌드를 선택하면 커밋이 푸시될 때마다 프로덕션 빌드에서 새로 복사본이 만들어집니다. 스테이징에서 개발로 되돌려진 브랜치는 " "자동으로 '아무 것도 하지 않음'으로 설정됩니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:320 msgid "**Modules installation**" msgstr "**모듈 설치**" #: ../../content/administration/odoo_sh/getting_started/branches.rst:322 msgid "" "Choose the modules to install automatically for your development builds." msgstr "개발 빌드에 자동으로 설치할 모듈을 선택합니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:327 msgid "" "*Install only my modules* will install the modules of the branch only. This " "is the default option. The :ref:`submodules ` " "are excluded." msgstr "" "*내 모듈만 설치*는 해당하는 브랜치의 모듈만 설치합니다. 기본 선택 사항입니다. :ref:`하위 모듈 `은 제외됩니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:329 msgid "" "*Full installation (all modules)* will install the modules of the branch, " "the modules included in the submodules and all standard modules of Odoo. " "When running the full installation, the test suite is disabled." msgstr "" "*전체 설치 (모든 모듈)*는 브랜치의 모듈, 하위 모듈에 포함된 모듈 및 Odoo의 모든 표준 모듈을 설치합니다. 전체 설치를 실행하면" " 테스트 집단이 비활성화됩니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:331 msgid "" "*Install a list of modules* will install the modules specified in the input " "just below this option. The names are the technical name of the modules, and" " they must be comma-separated." msgstr "" "*모듈 목록 설치*는 이 옵션의 바로 아래 입력란에 지정되어 있는 모듈을 설치합니다. 이름은 모듈의 기술명이며 쉼표로 구분되어야 합니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:334 msgid "" "If the tests are enabled, the standard Odoo modules suite can take up to 1 " "hour. This setting applies to development builds only. Staging builds " "duplicate the production build and the production build only installs base." msgstr "" "테스트를 활성화하게 되면 표준 Odoo 모듈 제품군의 경우 최대 1시간까지 소요될 수 있습니다. 개발 빌드에만 이 설정이 적용됩니다. " "스테이징 빌드는 프로덕션 빌드와 복제되고 프로덕션 빌드는 기본으로만 설치됩니다. " #: ../../content/administration/odoo_sh/getting_started/branches.rst:339 msgid "**Test suite**" msgstr "**테스트 집단**" #: ../../content/administration/odoo_sh/getting_started/branches.rst:341 msgid "" "For development branches, you can choose to enable or disable the test " "suite. It's enabled by default. When the test suite is enabled, you can " "restrict them by specifying test tags :ref:`test tags " "`." msgstr "" "개발 브랜치의 경우 테스트 도구 모음을 사용 또는 사용하지 않도록 선택할 수 있습니다. 사용하는 것이 기본값으로 되어 있습니다. 테스트 " "도구 모음이 활성화된 경우 :ref:`태그 테스트`를 지정하여 " "제한할 수 있습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:345 msgid "**Odoo Version**" msgstr "**Odoo 버전**" #: ../../content/administration/odoo_sh/getting_started/branches.rst:347 msgid "" "For development branches only, you can change the version of Odoo, should " "you want to test upgraded code or develop features while your production " "database is in the process of being upgraded to a newer version." msgstr "" "개발 브랜치에 한해, 프로덕션 데이터베이스가 최신 버전으로 업그레이드되는 동안 업그레이드된 코드를 테스트하거나 기능을 개발하려는 경우에 " "Odoo 버전을 변경할 수 있습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:350 msgid "" "In addition, for each version you have two options regarding the code " "update." msgstr "또한 각 버전별로 코드 업데이트와 관련된 옵션이 두 가지 있습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:352 msgid "" "You can choose to benefit from the latest bug, security and performance " "fixes automatically. The sources of your Odoo server will be updated weekly." " This is the 'Latest' option." msgstr "" "최신 버그, 보안 및 성능 수정 사항이 자동으로 적용되도록 선택할 수 있습니다. Odoo 서버의 소스는 매주 업데이트됩니다. 현재는 " "'최신' 상태입니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:354 msgid "" "You can choose to pin the Odoo sources to a specific revision by selecting " "them from a list of dates. Revisions will expire after 3 months. You will be" " notified by mail when the expiration date approaches and if you don't take " "action afterwards, you will automatically be set to the latest revision." msgstr "" "날짜 목록에서 Odoo 소스를 선택하여 특정한 개정판에 핀고정하도록 선택할 수 있습니다. 개정판은 3개월 후에 만료됩니다. 만료일에 " "가까워지면 메일로 알림을 받게 되며 이후에도 아무 조치를 취하지 않을 경우 자동으로 최신 개정판으로 설정됩니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:359 msgid "**Custom domains**" msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:361 msgid "" "Here you can configure additional domains for the selected branch. It's " "possible to add other *.odoo.com* domains or your own custom domains. " "For the latter you have to:" msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:364 msgid "own or purchase the domain name," msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:365 msgid "add the domain name in this list," msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:366 msgid "" "in your registrar's domain name manager, configure the domain name with a " "``CNAME`` record set to your production database domain name." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:369 msgid "" "For instance, to associate *www.mycompany.com* to your database " "*mycompany.odoo.com*:" msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:371 msgid "" "in Odoo.sh, add *www.mycompany.com* in the custom domains of your project " "settings," msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:372 msgid "" "in your domain name manager (e.g. *godaddy.com*, *gandi.net*, *ovh.com*), " "configure *www.mycompany.com* with a ``CNAME`` record with as value " "*mycompany.odoo.com*." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:375 msgid "Bare domains (e.g. *mycompany.com*) are not accepted:" msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:377 msgid "they can only be configured using ``A`` records," msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:378 msgid "``A`` records only accept IP addresses as value," msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:379 msgid "" "the IP address of your database can change, following an upgrade, a hardware" " failure or your wish to host your database in another country or continent." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:382 msgid "" "Therefore, bare domains could suddenly no longer work because of this change" " of IP address." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:384 msgid "" "In addition, if you would like both *mycompany.com* and *www.mycompany.com* " "to work with your database, having the first redirecting to the second is " "amongst the `SEO best practices " "`_ (See *Provide" " one version of a URL to reach a document*) in order to have one dominant " "URL. You can therefore just configure *mycompany.com* to redirect to " "*www.mycompany.com*. Most domain managers have the feature to configure this" " redirection. This is commonly called a web redirection." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:391 msgid "**HTTPS/SSL**" msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:393 msgid "" "If the redirection is correctly set up, the platform will automatically " "generate an SSL certificate with `Let's Encrypt " "`_ within the hour and your domain will be " "accessible through HTTPS." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:397 msgid "" "While it is currently not possible to configure your own SSL certificates on" " the Odoo.sh platform we are considering the feature if there is enough " "demand." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:401 msgid "**SPF and DKIM compliance**" msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:403 msgid "" "In case the domain of your users email addresses use SPF (Sender Policy " "Framework) or DKIM (DomainKeys Identified Mail), don't forget to authorize " "Odoo as a sending host in your domain name settings to increase the " "deliverability of your outgoing emails. The configuration steps are " "explained in the documentation about :ref:`SPF " "` and :ref:`DKIM " "`." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:410 msgid "" "Forgetting to configure your SPF or DKIM to authorize Odoo as a sending host" " can lead to the delivery of your emails as spam in your contacts inbox." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:414 msgid "Shell commands" msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:416 msgid "" "In the top right-hand corner of the view, different shell commands are " "available." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:421 msgid "" "Each command can be copied in the clipboard to be used in a terminal, and " "some of them can be used directly from Odoo.sh by clicking the *run* button " "in such case a popup will prompt the user in order to define eventual " "placeholders such as ````, ````, ..." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:427 msgid "Clone" msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:429 msgid "Download the Git repository." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:435 msgid "Clones the repository *odoo/odoo*." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:437 msgid "" ":code:`--recurse-submodules`: Downloads the submodules of your repository. " "Submodules included in the submodules are downloaded as well." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:438 msgid "" ":code:`--branch`: checks out a specific branch of the repository, in this " "case *master*." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:440 msgid "" "The *run* button is not available for this command, as it is meant to be " "used on your machines." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:443 msgid "Fork" msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:445 msgid "Create a new branch based on the current branch." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:451 msgid "" "Creates a new branch called *feature-1* based on the branch *master*, and " "then checkouts it." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:457 msgid "Uploads the new branch *feature-1* on your remote repository." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:460 msgid "Merge" msgstr "병합" #: ../../content/administration/odoo_sh/getting_started/branches.rst:462 msgid "Merge the current branch in another branch." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:468 msgid "Merges the branch *staging-1* in the current branch." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:474 #: ../../content/administration/odoo_sh/getting_started/branches.rst:547 msgid "" "Uploads the changes you just added in the *master* branch on your remote " "repository." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:477 msgid "SSH" msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:482 msgid "" "In order to use SSH, you have to set up your profile SSH public key (if it " "is not already done). To do so, follow these steps:" msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:485 msgid "" "`Generate a new SSH key `_" msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:487 msgid "" "`Copy the SSH key to your clipboard " "`_ (only apply the step 1)" msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:490 msgid "Paste the copied content to your profile SSH keys and press \"Add\"" msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:495 msgid "The key should appear below" msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:501 msgid "Connection" msgstr "연결" #: ../../content/administration/odoo_sh/getting_started/branches.rst:503 msgid "" "To connect to your builds using ssh use the following command in a terminal:" msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:509 msgid "" "You will find a shortcut for this command into the SSH tab in the upper " "right corner." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:514 msgid "" "Provided you have the :ref:`correct access rights ` on the project, you'll be granted ssh access to the" " build." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:518 msgid "" "Long running ssh connections are not guaranteed. Idle connections will be " "disconnected in order to free up resources." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:522 msgid "Submodule" msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:524 msgid "" "Add a branch from another repository in your current branch as a " "*submodule*." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:526 msgid "" "*Submodules* allows you to use modules from other repositories in your " "project." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:528 msgid "" "The submodules feature is detailed in the chapter :ref:`Submodules ` of this documentation." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:535 msgid "" "Adds the branch *master* of the repository ** as a submodule under the " "path ** in your current branch." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:541 msgid "Commits all your current changes." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:552 msgid "Delete a branch from your repository." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:558 msgid "Deletes the branch in your remote repository." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:564 msgid "Deletes the branch in your local copy of the repository." msgstr "" #: ../../content/administration/odoo_sh/getting_started/builds.rst:6 msgid "Builds" msgstr "" #: ../../content/administration/odoo_sh/getting_started/builds.rst:11 msgid "" "In Odoo.sh, a build is considered as a database loaded by an Odoo server " "(`odoo/odoo `_ & `odoo/enterprise " "`_) running on a specific revision of " "your project repository in a containerized environment. Its purpose is to " "test the well-behavior of the server, the database and the features with " "this revision." msgstr "" #: ../../content/administration/odoo_sh/getting_started/builds.rst:20 msgid "" "In this view, a row represents a branch, and a cell of a row represents a " "build of this branch." msgstr "" #: ../../content/administration/odoo_sh/getting_started/builds.rst:22 msgid "" "Most of the time, builds are created following pushes on your Github " "repository branches. They can be created as well when you do other " "operations, such as importing a database on Odoo.sh or asking a rebuild for " "a branch in your project." msgstr "" #: ../../content/administration/odoo_sh/getting_started/builds.rst:26 msgid "" "A build is considered successful if no errors or warnings come up during its" " creation. A successful build is highlighted in green." msgstr "" #: ../../content/administration/odoo_sh/getting_started/builds.rst:29 msgid "" "A build is considered failed if errors come up during its creation. A failed" " build is highlighted in red." msgstr "" #: ../../content/administration/odoo_sh/getting_started/builds.rst:32 msgid "" "If warnings come up during the creation, but there are no errors, the build " "is considered almost successful. It is highlighted in yellow to notify the " "developer warnings were raised." msgstr "" "생성 중에 경고가 표시되더라도 오류가 없으면 빌드가 거의 성공한 것으로 간주합니다. 개발자에게 경고가 발생했음을 알리기 위해 노란색으로 " "강조 표시됩니다." #: ../../content/administration/odoo_sh/getting_started/builds.rst:35 msgid "" "Builds do not always create a database from scratch. For instance, when " "pushing a change on the production branch, the build created just starts the" " server with your new revision and tries to load the current production " "database on it. If no errors come up, the build is considered successful, " "and otherwise failed." msgstr "" "빌드에서 항상 기초부터 데이터베이스가 생성되는 것은 아닙니다. 예를 들어, 프로덕션 브랜치에 변경 사항을 적용할 때 생성된 빌드로는 " "새로운 개정판으로 서버가 시작되고 여기에 현재 프로덕션 데이터베이스를 로드하려고 시도합니다. 오류가 발생하지 않으면 빌드가 성공한 것으로" " 간주되고 그렇지 않으면 실패한 것으로 간주됩니다." #: ../../content/administration/odoo_sh/getting_started/builds.rst:46 msgid "" "The first build of a production branch creates a database from scratch. If " "this build is successful, this database is considered as the production " "database of your project." msgstr "" "프로덕션 브랜치의 첫 번째 빌드는 기초부터 데이터베이스를 생성합니다. 이 빌드가 성공하면 데이터베이스는 프로젝트의 프로덕션 데이터베이스로" " 간주됩니다." #: ../../content/administration/odoo_sh/getting_started/builds.rst:49 msgid "" "From then, pushes on the production branch will create new builds that " "attempt to load the database using a server running with the new revision." msgstr "그런 다음 프로덕션 브랜치를 적용하면 새 개정판으로 실행되는 서버에서 데이터베이스를 로드하는 새로운 빌드가 생성됩니다." #: ../../content/administration/odoo_sh/getting_started/builds.rst:52 msgid "" "If the build is successful, or has warnings but no errors, the production " "database will now run with this build, along with the revision associated to" " this build." msgstr "" "빌드가 성공했거나, 경고는 있으나 오류가 없는 경우 프로덕션 데이터베이스는 이제 해당 빌드에 연결된 개정판과 함께 이 빌드로 실행됩니다." #: ../../content/administration/odoo_sh/getting_started/builds.rst:55 msgid "" "If the build fails to load or update the database, then the previous " "successful build is re-used to load the database, and therefore the database" " will run using a server running with the previous successful revision." msgstr "" "빌드에서 데이터베이스를 로드하거나 업데이트하는 데 실패하면 이전에 성공한 빌드로 다시 데이터베이스를 로드하므로 데이터베이스는 이전에 " "성공한 개정판으로 실행되는 서버에서 실행됩니다." #: ../../content/administration/odoo_sh/getting_started/builds.rst:59 msgid "" "The build used to run the production database is always the first of the " "builds list. If a build fails, it is put after the build currently running " "the production database." msgstr "" "프로덕션 데이터베이스 실행에 사용되는 빌드는 항상 빌드 목록의 첫 번째에 위치합니다. 빌드가 실패하면 현재 프로덕션 데이터베이스를 실행 " "중인 빌드 뒤에 배치됩니다." #: ../../content/administration/odoo_sh/getting_started/builds.rst:65 msgid "" "Staging builds duplicate the production database, and try to load this " "duplicate with the revisions of the staging branches." msgstr "스테이징 브랜치는 프로덕션 데이터베이스를 복제하고 해당 복제본을 스테이징 브랜치의 개정판과 함께 로드하게 됩니다." #: ../../content/administration/odoo_sh/getting_started/builds.rst:68 msgid "" "Each time you push a new revision on a staging branch, the build created " "uses a new copy of the production database. The databases are not re-used " "between builds of the same branch. This ensures:" msgstr "" "스테이징 브랜치에 새 개정판을 적용할 때마다 생성된 빌드는 프로덕션 데이터베이스의 새 복사본을 사용합니다. 데이터베이스는 동일한 브랜치에" " 있는 빌드 사이에는 재사용되지 않습니다. 이를 통해 다음과 같은 내용이 보장됩니다." #: ../../content/administration/odoo_sh/getting_started/builds.rst:71 msgid "" "staging builds use databases that are close to what the production looks " "like, so you do not make your tests with outdated data," msgstr "스테이징 빌드는 프로덕션 환경과 유사한 데이터베이스를 사용하므로 오래된 데이터로 테스트를 만들지 않습니다." #: ../../content/administration/odoo_sh/getting_started/builds.rst:74 msgid "" "you can play around as much as you want in the same staging database, and " "you can then ask for a rebuild when you want to restart with a new copy of " "the production." msgstr "" "동일한 스테이징 데이터베이스에서 마음껏 작업을 수행할 수 있으며, 프로덕션의 새 복사본으로 다시 시작하려는 경우 다시 빌드를 요청할 수 " "있습니다." #: ../../content/administration/odoo_sh/getting_started/builds.rst:77 msgid "" "Nevertheless, this means that if you make configuration changes in staging " "databases and do not apply them in the production, they will not be passed " "on the next build of the same staging branch." msgstr "" "그럼에도 불구하고 스테이징 데이터베이스에서 환경 설정을 변경한 후 프로덕션에 적용하지 않으면 동일한 스테이징 브랜치의 다음 빌드로 " "이전되지 않습니다." #: ../../content/administration/odoo_sh/getting_started/builds.rst:83 msgid "" "Development builds create new databases, load the demo data and run the unit" " tests." msgstr "개발 빌드는 새 데이터베이스 생성, 데모 데이터 로드 및 단위 테스트 실행을 하게 됩니다." #: ../../content/administration/odoo_sh/getting_started/builds.rst:85 msgid "" "A build will be considered failed and highlighted in red if tests fail " "during the installation, as they are meant to raise errors if something " "wrong occurs." msgstr "" #: ../../content/administration/odoo_sh/getting_started/builds.rst:88 msgid "" "If all tests pass, and there is no error, the build will be considered " "successful." msgstr "" #: ../../content/administration/odoo_sh/getting_started/builds.rst:90 msgid "" "According to the list of modules to install and test, a development build " "can take up to 1 hour to be ready. This is due to the large number of tests " "set in the default Odoo modules suite." msgstr "" #: ../../content/administration/odoo_sh/getting_started/builds.rst:94 msgid "Features" msgstr "기능" #: ../../content/administration/odoo_sh/getting_started/builds.rst:96 msgid "" "The production branch will always appear first, and then the other branches " "are ordered by last build created. You can filter out the branches." msgstr "" #: ../../content/administration/odoo_sh/getting_started/builds.rst:102 msgid "" "For each branch, you can access the last build's database using the " "*Connect* link and jump to the branch code using the *Github* link. For " "other branches than the production, you can create a new build which will " "use the latest revision of the branch using the link *rebuild*. This last " "link is not available when there is already a build in progress for the " "branch." msgstr "" #: ../../content/administration/odoo_sh/getting_started/builds.rst:110 msgid "" "For each build, you can access the revision changes using the button with " "the Github icon. You can access the build's database as the administrator " "using the *Connect* button. Also, you can access the database with another " "user using the *Connect as* button, in the dropdown menu of the *Connect* " "button." msgstr "" #: ../../content/administration/odoo_sh/getting_started/builds.rst:122 msgid "" "In the dropdown menu of the build, you can access the same features than in " ":ref:`the branches view `: *Logs*, *Web" " Shell*, *Editor*, *Outgoing e-mails*. You also have the possibility to " "*Download a dump* of the build's database." msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:6 msgid "Create your project" msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:9 msgid "Deploy your platform" msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:11 msgid "" "Go to `Odoo.sh `_ and hit the *Deploy your platform* " "button." msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:17 msgid "Sign in with Github" msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:19 msgid "" "Sign in with your Github account. If you do not have an account yet, hit the" " *Create an account* link." msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:26 msgid "Authorize Odoo.sh" msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:28 msgid "" "Grant Odoo.sh the required accesses to your account by clicking the " "*Authorize* button." msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:33 msgid "Odoo.sh basically needs:" msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:35 msgid "to know your Github login and email," msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:36 msgid "to create a new repository in case you decide to start from scratch," msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:37 msgid "" "to read your existing repositories, including the ones of your " "organizations, in case you want to start from an existing repository," msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:39 msgid "to create a webhook to be notified each time you push changes," msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:40 msgid "" "to commit changes to make your deployment easier, merging branches or adding" " new `submodules `_ for" " example." msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:44 msgid "Submit your project" msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:46 msgid "" "Choose if you want to start from scratch by creating a new repository, or if" " you want to use an existing repository." msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:49 msgid "Then, choose a name or select the repository you want to use." msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:51 msgid "" "Choose the Odoo version you want to use. If you plan to import an existing " "database or an existing set of applications, you might need to choose the " "according version. If you start from scratch, use the latest version." msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:55 msgid "" "Enter your *subscription code*. This is also called *subscription referral*," " *contract number* or *activation code*." msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:58 msgid "" "It should be the code of your Enterprise subscription that includes Odoo.sh." msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:60 msgid "" "Partners can use their partnership codes to start a trial. Should their " "clients start a project, they ought to get an Enterprise subscription " "including Odoo.sh and use its subscription code. The partner will get 50% of" " the amount back as commission. Contact your sales representative or account" " manager in order to get it." msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:65 msgid "" "When submitting the form, if you are notified your subscription is not " "valid, it either means:" msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:67 msgid "it is not an existing subscription," msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:68 msgid "it is not a partnership subscription," msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:69 msgid "it is an enterprise subscription, but which does not include Odoo.sh," msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:70 msgid "" "it is neither a partnership subscription or an enterprise subscription (e.g." " an online subscription)." msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:73 msgid "" "In case of doubt with your subscription, please contact the `Odoo support " "`_." msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:80 msgid "You're done !" msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:82 msgid "" "You can start using Odoo.sh. Your first build is about to be created. You " "will soon be able to connect to your first database." msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:91 msgid "Import your database" msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:93 msgid "" "You can import your database in your Odoo.sh project as long as it is in a " ":doc:`supported version ` of " "Odoo." msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:97 msgid "Push your modules in production" msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:99 msgid "" "If you use community or custom modules, add them in a branch in your Github " "repository. Databases hosted on the Odoo.com online platform do not have any" " custom modules. Users of these databases can therefore skip this step." msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:103 msgid "" "You can structure your modules as you wish, Odoo.sh will automatically " "detect the folders containing Odoo addons. For instance, you can put all " "your modules folder in the root directory of your repository, or group the " "modules in folders by categories that you define (accounting, project, ...)." msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:108 msgid "" "For community modules available in public Git repositories, you can also " "consider to add them using :ref:`Submodules `." msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:111 msgid "" "Then, either :ref:`make this branch the production branch `, or :ref:`merge it into your production " "branch `." msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:115 msgid "Download a backup" msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:118 msgid "On-premise databases" msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:120 msgid "" "Access the URL :file:`/web/database/manager` of your on-premise database and" " download a backup." msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:124 msgid "" "If you cannot access the database manager, it may have been disabled by your" " system administrator. See the :ref:`database manager security documentation" " `." msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:127 msgid "" "You will need the master password of your database server. If you do not " "have it, contact your system administrator." msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:133 msgid "Choose a zip including the filestore as the backup format." msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:139 msgid "Odoo Online databases" msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:141 msgid "" "`Access your databases manager " "`_ and download a backup of " "your database." msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:149 msgid "Online versions (e.g. *saas-**) are not supported on Odoo.sh." msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:152 msgid "Upload the backup" msgstr "백업 업로드하기" #: ../../content/administration/odoo_sh/getting_started/create.rst:154 msgid "" "Then, in your Odoo.sh project, in the backups tab of your production branch," " import the backup you just downloaded." msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:160 msgid "" "Once the backup imported, you can access the database using the *Connect* " "button in the history of the branch." msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:167 msgid "Check your outgoing email servers" msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:169 msgid "" "There is a default mail server provided with Odoo.sh. To use it, there must " "be no enabled outgoing mail server configured in your database in " ":menuselection:`Settings --> Technical --> Outgoing Mail Servers` " "(:ref:`Developer mode ` must be activated)." msgstr "" "Odoo.sh 와 함께 기본 메일 서버를 제공합니다. 이를 사용하시려면 :menuselection:`설정 --> 기술 --> 발신 메일 " "서버` (:ref:`개발자 모드`가 활성화되어야 함).에서 데이터베이스에 구성한 발신 메일 서버가 활성화되어" " 있지 않아야 합니다." #: ../../content/administration/odoo_sh/getting_started/create.rst:174 msgid "" "After the import of your database, all outgoing email servers are disabled " "so you use the Odoo.sh email server provided by default." msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:178 msgid "" "Port 25 is (and will stay) closed. If you want to connect to an external " "SMTP server, you should use ports 465 and 587." msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:182 msgid "Check your scheduled actions" msgstr "예약된 활동을 확인하세요." #: ../../content/administration/odoo_sh/getting_started/create.rst:184 msgid "All scheduled actions are disabled after the import." msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:186 msgid "" "This is to prevent your newly imported database to perform actions that " "could impact your running production, such as sending the mails remaining in" " the queue, processing mass mailings, or third-party services " "synchronization (Calendars, files hosting, ...)." msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:190 msgid "" "If you plan to make the imported database your production, enable the " "scheduled actions you need. You can check what is enabled in the database of" " origin and enable the same actions in the imported database. Scheduled " "actions are located under :menuselection:`Settings --> Technical --> " "Automation --> Scheduled Actions`." msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:196 msgid "Register your subscription" msgstr "구독 상품 등록하기" #: ../../content/administration/odoo_sh/getting_started/create.rst:198 msgid "Your subscription is unlinked after the import." msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:200 msgid "" "The imported database is considered a duplicate by default and the " "enterprise subscription is therefore removed, as you can only have one " "database linked per subscription." msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:203 msgid "" "If you plan to make it your production, unlink your former database from the" " subscription, and register the newly imported database. Read the " ":doc:`database registration documentation <../../maintain/on_premise>` for " "instructions." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:3 msgid "Your first module" msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:8 msgid "" "This chapter helps you to create your first Odoo module and deploy it in " "your Odoo.sh project." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:10 msgid "" "This tutorial requires :ref:`you created a project on Odoo.sh `, and you know your Github repository's URL." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:13 msgid "Basic use of Git and Github is explained." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:15 msgid "The below assumptions are made:" msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:17 msgid "" "*~/src* is the directory where are located the Git repositories related to " "your Odoo projects," msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:18 msgid "*odoo* is the Github user," msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:19 msgid "*odoo-addons* is the Github repository," msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:20 msgid "*feature-1* is the name of a development branch," msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:21 msgid "*master* is the name of the production branch," msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:22 msgid "*my_module* is the name of the module." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:24 msgid "Replace these by the values of your choice." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:27 msgid "Create the development branch" msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:30 msgid "From Odoo.sh" msgstr "Odoo.sh 에서" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:32 msgid "In the branches view:" msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:34 msgid "hit the :code:`+` button next to the development stage," msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:35 msgid "choose the branch *master* in the *Fork* selection," msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:36 msgid "type *feature-1* in the *To* input." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:38 msgid "|pic1| |pic2|" msgstr "|pic1| |pic2|" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:40 msgid "pic1" msgstr "pic1" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:43 msgid "pic2" msgstr "pic2" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:46 msgid "" "Once the build created, you can access the editor and browse to the folder " "*~/src/user* to access to the code of your development branch." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:56 msgid "From your computer" msgstr "컴퓨터에서" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:58 msgid "Clone your Github repository on your computer:" msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:67 msgid "Create a new branch:" msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:74 msgid "Create the module structure" msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:77 msgid "Scaffolding the module" msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:79 msgid "" "While not necessary, scaffolding avoids the tedium of setting the basic Odoo" " module structure. You can scaffold a new module using the executable *odoo-" "bin*." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:82 msgid "From the Odoo.sh editor, in a terminal:" msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:88 msgid "" "Or, from your computer, if you have an :doc:`installation of Odoo " "<../../install/source>`:" msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:94 msgid "" "If you do not want to bother installing Odoo on your computer, you can also " ":download:`download this module structure template " "` in which you replace every occurrences of " "*my_module* to the name of your choice." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:98 msgid "The below structure will be generated:" msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:121 msgid "" "Do not use special characters other than the underscore ( _ ) for your " "module name, not even an hyphen ( - ). This name is used for the Python " "classes of your module, and having classes name with special characters " "other than the underscore is not valid in Python." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:125 msgid "Uncomment the content of the files:" msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:127 msgid "*models/models.py*, an example of model with its fields," msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:129 msgid "" "*views/views.xml*, a tree and a form view, with the menus opening them," msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:131 msgid "*demo/demo.xml*, demo records for the above example model," msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:133 msgid "" "*controllers/controllers.py*, an example of controller implementing some " "routes," msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:135 msgid "" "*views/templates.xml*, two example qweb views used by the above controller " "routes," msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:137 msgid "" "*__manifest__.py*, the manifest of your module, including for instance its " "title, description and data files to load. You just need to uncomment the " "access control list data file:" msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:146 msgid "Manually" msgstr "수동" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:148 msgid "" "If you want to create your module structure manually, you can follow the " ":doc:`/developer/tutorials/getting_started` tutorial to understand the " "structure of a module and the content of each file." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:153 msgid "Push the development branch" msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:155 msgid "Stage the changes to be committed" msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:161 #: ../../content/administration/odoo_sh/getting_started/first_module.rst:395 msgid "Commit your changes" msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:167 msgid "Push your changes to your remote repository" msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:169 msgid "From an Odoo.sh editor terminal:" msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:175 msgid "" "The above command is explained in the section :ref:`Commit & Push your " "changes ` of the :ref:`Online " "Editor ` chapter. It includes the " "explanation regarding the fact you will be prompted to type your username " "and password, and what to do if you use the two-factor authentication." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:183 #: ../../content/administration/odoo_sh/getting_started/first_module.rst:383 #: ../../content/administration/odoo_sh/getting_started/first_module.rst:409 msgid "Or, from your computer terminal:" msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:189 msgid "" "You need to specify *-u origin feature-1* for the first push only. From that" " point, to push your future changes from your computer, you can simply use" msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:197 msgid "Test your module" msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:199 msgid "" "Your branch should appear in your development branches in your project." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:204 msgid "" "In the branches view of your project, you can click on your branch name in " "the left navigation panel to access its history." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:210 msgid "" "You can see here the changes you just pushed, including the comment you set." " Once the database ready, you can access it by clicking the *Connect* " "button." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:216 msgid "" "If your Odoo.sh project is configured to install your module automatically, " "you will directly see it amongst the database apps. Otherwise, it will be " "available in the apps to install." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:220 msgid "" "You can then play around with your module, create new records and test your " "features and buttons." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:223 msgid "Test with the production data" msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:225 msgid "" "You need to have a production database for this step. You can create it if " "you do not have it yet." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:227 msgid "" "Once you tested your module in a development build with the demo data and " "believe it is ready, you can test it with the production data using a " "staging branch." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:230 msgid "You can either:" msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:232 msgid "" "Make your development branch a staging branch, by drag and dropping it onto " "the *staging* section title." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:238 msgid "" "Merge it in an existing staging branch, by drag and dropping it onto the " "given staging branch." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:243 #: ../../content/administration/odoo_sh/getting_started/first_module.rst:289 msgid "You can also use the :code:`git merge` command to merge your branches." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:245 msgid "" "This will create a new staging build, which will duplicate the production " "database and make it run using a server updated with your latest changes of " "your branch." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:251 #: ../../content/administration/odoo_sh/getting_started/first_module.rst:297 msgid "Once the database ready, you can access it using the *Connect* button." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:256 #: ../../content/administration/odoo_sh/getting_started/first_module.rst:300 msgid "Install your module" msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:258 msgid "" "Your module will not be installed automatically, you have to install it from" " the apps menu. Indeed, the purpose of the staging build is to test the " "behavior of your changes as it would be on your production, and on your " "production you would not like your module to be installed automatically, but" " on demand." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:263 msgid "" "Your module may not appear directly in your apps to install either, you need" " to update your apps list first:" msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:266 msgid "Activate the :ref:`developer mode `" msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:267 msgid "in the apps menu, click the *Update Apps List* button," msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:268 msgid "in the dialog that appears, click the *Update* button." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:273 msgid "Your module will then appear in the list of available apps." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:279 msgid "Deploy in production" msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:281 msgid "" "Once you tested your module in a staging branch with your production data, " "and believe it is ready for production, you can merge your branch in the " "production branch." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:284 msgid "Drag and drop your staging branch on the production branch." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:291 msgid "" "This will merge the latest changes of your staging branch in the production " "branch, and update your production server with these latest changes." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:302 msgid "" "Your module will not be installed automatically, you have to install it " "manually as explained in the :ref:`above section about installing your " "module in staging databases `." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:308 msgid "Add a change" msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:310 msgid "" "This section explains how to add a change in your module by adding a new " "field in a model and deploy it." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:315 msgid "From the Odoo.sh editor," msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:314 msgid "browse to your module folder *~/src/user/my_module*," msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:315 msgid "then, open the file *models/models.py*." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:321 msgid "Or, from your computer," msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:318 msgid "" "use the file browser of your choice to browse to your module folder " "*~/src/odoo-addons/my_module*," msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:320 msgid "" "then, open the file *models/models.py* using the editor of your choice, such" " as *Atom*, *Sublime Text*, *PyCharm*, *vim*, ..." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:323 msgid "Then, after the description field" msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:329 msgid "Add a datetime field" msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:335 msgid "Then, open the file *views/views.xml*." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:337 #: ../../content/administration/odoo_sh/getting_started/first_module.rst:473 msgid "After" msgstr "이후" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:343 #: ../../content/administration/odoo_sh/getting_started/first_module.rst:450 #: ../../content/administration/odoo_sh/getting_started/first_module.rst:467 #: ../../content/administration/odoo_sh/getting_started/first_module.rst:479 msgid "Add" msgstr "추가" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:349 msgid "" "These changes alter the database structure by adding a column in a table, " "and modify a view stored in database." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:352 msgid "" "In order to be applied in existing databases, such as your production " "database, these changes requires the module to be updated." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:355 msgid "" "If you would like the update to be performed automatically by the Odoo.sh " "platform when you push your changes, increase your module version in its " "manifest." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:358 msgid "Open the module manifest *__manifest__.py*." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:366 #: ../../content/administration/odoo_sh/getting_started/first_module.rst:504 msgid "with" msgstr "조회" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:372 msgid "" "The platform will detect the change of version and trigger the update of the" " module upon the new revision deployment." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:375 msgid "Browse to your Git folder." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:377 msgid "Then, from an Odoo.sh terminal:" msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:389 msgid "Then, stage your changes to be committed" msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:401 msgid "Push your changes:" msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:403 msgid "From an Odoo.sh terminal:" msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:415 msgid "The platform will then create a new build for the branch *feature-1*." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:420 msgid "" "Once you tested your changes, you can merge your changes in the production " "branch, for instance by drag-and-dropping the branch on the production " "branch in the Odoo.sh interface. As you increased the module version in the " "manifest, the platform will update the module automatically and your new " "field will be directly available. Otherwise you can manually update the " "module within the apps list." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:426 msgid "Use an external Python library" msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:428 msgid "" "If you would like to use an external Python library which is not installed " "by default, you can define a *requirements.txt* file listing the external " "libraries your modules depends on." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:432 msgid "" "It is not possible to install or upgrade system packages on an Odoo.sh " "database (e.g., apt packages). However, under specific conditions, packages " "can be considered for installation. This also applies to **Python modules** " "requiring system packages for their compilation, and **third-party Odoo " "modules**." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:436 msgid "**PostgreSQL extensions** are not supported on Odoo.sh." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:437 msgid "" "For more information, consult our `FAQ " "`_." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:439 msgid "" "The platform will use this file to automatically install the Python " "libraries your project needs." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:441 msgid "" "The feature is explained in this section by using the `Unidecode library " "`_ in your module." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:444 msgid "Create a file *requirements.txt* in the root folder of your repository" msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:446 msgid "" "From the Odoo.sh editor, create and open the file " "~/src/user/requirements.txt." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:448 msgid "" "Or, from your computer, create and open the file ~/src/odoo-" "addons/requirements.txt." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:456 msgid "" "Then use the library in your module, for instance to remove accents from " "characters in the name field of your model." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:459 msgid "Open the file *models/models.py*." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:461 msgid "Before" msgstr "이전" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:494 msgid "" "Adding a Python dependency requires a module version increase for the " "platform to install it." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:496 msgid "Edit the module manifest *__manifest__.py*" msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:510 msgid "Stage and commit your changes:" msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:518 msgid "Then, push your changes:" msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:520 msgid "In an Odoo.sh terminal:" msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:526 msgid "In your computer terminal:" msgstr "" #: ../../content/administration/odoo_sh/getting_started/online-editor.rst:6 msgid "Online Editor" msgstr "" #: ../../content/administration/odoo_sh/getting_started/online-editor.rst:11 msgid "" "The online editor allows you to edit the source code of your builds from a " "web browser. It also gives you the possibility to open terminals, Python " "consoles, Odoo Shell consoles and `Notebooks " "`_." msgstr "" #: ../../content/administration/odoo_sh/getting_started/online-editor.rst:18 msgid "" "You can access the editor of a build through :ref:`the branches tabs " "`, :ref:`the builds dropdown menu " "` or by adding */odoo-sh/editor*" " to your build domain name (e.g. *https://odoo-addons-" "master-1.dev.odoo.com/odoo-sh/editor*)." msgstr "" #: ../../content/administration/odoo_sh/getting_started/online-editor.rst:25 msgid "Edit the source code" msgstr "" #: ../../content/administration/odoo_sh/getting_started/online-editor.rst:27 msgid "The working directory is composed of the following folders:" msgstr "" #: ../../content/administration/odoo_sh/getting_started/online-editor.rst:49 msgid "" "You can edit the source code (files under */src*) in development and staging" " builds." msgstr "" #: ../../content/administration/odoo_sh/getting_started/online-editor.rst:52 msgid "" "Your changes won't be propagated to a new build, you must commit them in " "your source code if you want to make them persist." msgstr "" #: ../../content/administration/odoo_sh/getting_started/online-editor.rst:56 msgid "" "For production builds, the source code is read-only, because applying local " "changes on a production server is not a good practice." msgstr "" #: ../../content/administration/odoo_sh/getting_started/online-editor.rst:59 msgid "" "The source code of your Github repository is located under */src/user*," msgstr "" #: ../../content/administration/odoo_sh/getting_started/online-editor.rst:60 msgid "The source code of Odoo is located under" msgstr "" #: ../../content/administration/odoo_sh/getting_started/online-editor.rst:62 msgid "*/src/odoo* (`odoo/odoo `_)," msgstr "" #: ../../content/administration/odoo_sh/getting_started/online-editor.rst:63 msgid "" "*/src/enterprise* (`odoo/enterprise `_)," msgstr "" #: ../../content/administration/odoo_sh/getting_started/online-editor.rst:64 msgid "" "*/src/themes* (`odoo/design-themes `_)." msgstr "" #: ../../content/administration/odoo_sh/getting_started/online-editor.rst:66 msgid "" "To open a file in the editor, just double-click on it in the file browser " "panel on the left." msgstr "" #: ../../content/administration/odoo_sh/getting_started/online-editor.rst:71 msgid "" "You can then begin to make your changes. You can save your changes with the " "menu :menuselection:`File --> Save .. File` or by hitting the :kbd:`Ctrl+S` " "shortcut." msgstr "" #: ../../content/administration/odoo_sh/getting_started/online-editor.rst:77 msgid "" "If you save a Python file which is under your Odoo server addons path, Odoo " "will detect it and reload automatically so your changes are reflected " "immediately, without having to restart the server manually." msgstr "" #: ../../content/administration/odoo_sh/getting_started/online-editor.rst:84 msgid "" "However, if the change is a data stored in database, such as the label of a " "field, or a view, you have to update the according module to apply the " "change. You can update the module of the currently opened file by using the " "menu :menuselection:`Odoo --> Update current module`. Note that the file " "considered as currently opened is the file focused in the text editor, not " "the file highlighted in the file browser." msgstr "" "하지만 필드 또는 뷰의 레이블 변경과 같이 데이터베이스에 저장된 데이터와 관련된 수정 사항인 경우 해당 모듈을 업데이트하여 변경 사항을 " "구현해야 합니다. 현재 열려 있는 파일의 모듈은 메뉴 :menuselection:`Odoo --> 현재 모듈 업데이트`를 사용하여 " "업데이트할 수 있습니다. 현재 열려 있는 것으로 간주되는 파일은 파일 브라우저에서 강조 표시된 파일이 아니라 텍스트 편집기에서 초점이 " "맞춰진 파일입니다." #: ../../content/administration/odoo_sh/getting_started/online-editor.rst:93 msgid "You can also open a terminal and execute the command:" msgstr "" #: ../../content/administration/odoo_sh/getting_started/online-editor.rst:102 msgid "Commit & Push your changes" msgstr "" #: ../../content/administration/odoo_sh/getting_started/online-editor.rst:104 msgid "" "You have the possibility to commit and push your changes to your Github " "repository." msgstr "" #: ../../content/administration/odoo_sh/getting_started/online-editor.rst:106 msgid "Open a terminal (:menuselection:`File --> New --> Terminal`)," msgstr "" #: ../../content/administration/odoo_sh/getting_started/online-editor.rst:107 msgid "Change the directory to *~/src/user* using :code:`cd ~/src/user`," msgstr "" #: ../../content/administration/odoo_sh/getting_started/online-editor.rst:108 msgid "Stage your changes using :code:`git add`," msgstr "" #: ../../content/administration/odoo_sh/getting_started/online-editor.rst:109 msgid "Commit your changes using :code:`git commit`," msgstr "" #: ../../content/administration/odoo_sh/getting_started/online-editor.rst:110 msgid "Push your changes using :code:`git push https HEAD:`." msgstr "" #: ../../content/administration/odoo_sh/getting_started/online-editor.rst:112 msgid "In this last command," msgstr "" #: ../../content/administration/odoo_sh/getting_started/online-editor.rst:114 msgid "" "*https* is the name of your *HTTPS* Github remote repository (e.g. " "https://github.com/username/repository.git)," msgstr "" #: ../../content/administration/odoo_sh/getting_started/online-editor.rst:116 msgid "HEAD is the reference to the latest revision you committed," msgstr "" #: ../../content/administration/odoo_sh/getting_started/online-editor.rst:117 msgid "" " must be replaced by the name of the branch to which you want to " "push the changes, most-likely the current branch if you work in a " "development build." msgstr "" #: ../../content/administration/odoo_sh/getting_started/online-editor.rst:124 msgid "" "The SSH Github remote is not used because your SSH private key is not hosted" " in your build containers (for obvious security concerns) nor forwarded " "through an SSH Agent (as you access this editor through a web browser) and " "you therefore cannot authenticate yourself to Github using SSH. You have to " "use the HTTPS remote of your Github repository to push your changes, which " "is added automatically named as *https* in your Git remotes. You will be " "prompted to enter your Github username and password. If you activated the " "two-factor authentication on Github, you can create a `personal access token" " `_ and use it as password. Granting the ``repo`` permission " "suffices." msgstr "" "보안 고려 사항으로 인해 빌드 컨테이너에 SSH 개인 키가 없거나 웹 브라우저를 통해 이 편집기에 액세스하는 경우 SSH 에이전트를 통해" " 전달되기 때문에 SSH Github 리모트는 사용되지 않습니다. 따라서 SSH를 사용하여 Github에 인증할 수 없습니다. 대신, " "변경 사항을 푸시하려면 Git 리포지토리의 HTTPS 리모컨을 사용해야 하며, 이 리모컨은 자동으로 추가되고 Git 리모컨의 이름이 " "*https*로 지정됩니다. 이 과정에서 Github 사용자 이름과 비밀번호를 입력하라는 메시지가 표시됩니다. Github에서 2단계 " "인증을 사용 설정한 경우 `개인 액세스 토큰 `_을 생성하여 비밀번호로 사용할 수 있습니다. " "``리포지토리`` 권한을 부여하는 것이 적절합니다." #: ../../content/administration/odoo_sh/getting_started/online-editor.rst:137 msgid "" "The Git source folder *~/src/user* is not checked out on a branch but rather" " on a detached revision: This is because builds work on specific revisions " "rather than branches. In other words, this means you can have multiple " "builds on the same branch, but on different revisions." msgstr "" #: ../../content/administration/odoo_sh/getting_started/online-editor.rst:141 msgid "" "Once your changes are pushed, according to your :ref:`branch push behavior " "`, a new build may be created." " You can continue to work in the editor you pushed from, as it will have the" " same revision as the new build that was created, but always make sure to be" " in an editor of a build using the latest revision of your branch." msgstr "" #: ../../content/administration/odoo_sh/getting_started/online-editor.rst:148 msgid "Consoles" msgstr "" #: ../../content/administration/odoo_sh/getting_started/online-editor.rst:150 msgid "" "You can open Python consoles, which are `IPython interactive shells " "`_. One " "of the most interesting addition to use a Python console rather than a " "IPython shell within a terminal is the `rich display " "`_ capabilities. Thanks to this, you will be able to display objects" " in HTML." msgstr "" #: ../../content/administration/odoo_sh/getting_started/online-editor.rst:158 msgid "" "You can for instance display cells of a CSV file using `pandas " "`_." msgstr "" #: ../../content/administration/odoo_sh/getting_started/online-editor.rst:164 msgid "" "You can also open an Odoo Shell console to play around with the Odoo " "registry and model methods of your database. You can also directly read or " "write on your records." msgstr "" #: ../../content/administration/odoo_sh/getting_started/online-editor.rst:169 msgid "" "In an Odoo Console, transactions are automatically committed. This means, " "for instance, that changes in records are applied effectively in the " "database. If you change the name of a user, the name of the user is changed " "in your database as well. You therefore should use Odoo consoles carefully " "on production databases." msgstr "" #: ../../content/administration/odoo_sh/getting_started/online-editor.rst:174 msgid "" "You can use *env* to invoke models of your database registry, e.g. " ":code:`env['res.users']`." msgstr "" #: ../../content/administration/odoo_sh/getting_started/online-editor.rst:184 msgid "" "The class :code:`Pretty` gives you the possibility to easily display lists " "and dicts in a pretty way, using the `rich display " "`_ mentioned above." msgstr "" #: ../../content/administration/odoo_sh/getting_started/online-editor.rst:192 msgid "" "You can also use `pandas `_ to display graphs." msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:8 msgid "The settings allow you to manage the configuration of your project." msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:14 msgid "Project name" msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:16 msgid "The name of your project." msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:21 msgid "" "This defines the address that will be used to access your production " "database." msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:23 msgid "" "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." msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:29 msgid "Collaborators" msgstr "공동작업자" #: ../../content/administration/odoo_sh/getting_started/settings.rst:31 msgid "Manage the Github users who can access your project." msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:36 msgid "There are two levels of users:" msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:38 msgid "Admin: has access to all features of Odoo.sh." msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:39 msgid "" "User: does not have access to the project settings nor to the production and" " staging databases." msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:41 msgid "" "The user group is meant for developers who can make modifications in your " "code but are not allowed to access the production data. Users of this group " "cannot connect to the production and staging databases using the *1-click " "connect* feature, but they can of course use their regular account on these " "databases if they have one, using their regular credentials." msgstr "" "사용자 그룹은 코드 수정은 할 수 있지만 프로덕션 데이터에 액세스할 수 없는 개발자를 위한 것입니다. 이 그룹의 사용자는 *원클릭 연결*" " 기능을 사용하여 프로덕션 및 스테이지 데이터베이스에 연결할 수는 없으나, 데이터베이스에 일반 계정이 있는 경우 일반 자격 증명으로 " "사용할 수 있습니다." #: ../../content/administration/odoo_sh/getting_started/settings.rst:46 msgid "" "In addition, they cannot use the webshell nor have access to the server " "logs." msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:54 msgid "User" msgstr "사용자" #: ../../content/administration/odoo_sh/getting_started/settings.rst:55 msgid "Admin" msgstr "관리자" #: ../../content/administration/odoo_sh/getting_started/settings.rst:61 #: ../../content/administration/odoo_sh/getting_started/settings.rst:89 msgid "1-click connect" msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:69 #: ../../content/administration/odoo_sh/getting_started/settings.rst:97 msgid "Shell/SSH" msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:84 msgid "Production & Staging" msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:118 msgid "|green|\\*" msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:120 #: ../../content/administration/odoo_sh/getting_started/status.rst:3 msgid "Status" msgstr "상태" #: ../../content/administration/odoo_sh/getting_started/settings.rst:130 msgid "\\* Only in staging branches" msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:145 msgid "Public Access" msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:147 msgid "Allow public access to your development builds." msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:152 msgid "" "If activated, this option exposes the Builds page publicly, allowing " "visitors to connect to your development builds." msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:155 msgid "" "In addition, visitors have access to the logs, shell and mails of your " "development builds." msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:157 msgid "" "Production and staging builds are excluded, visitors can only see their " "status." msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:162 msgid "Custom domains" msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:164 msgid "" "To configure additional domains please refer to the corresponding branch's " ":ref:`settings tab `." msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:172 msgid "" "Configure the deploy keys for the private repositories you use as submodules" " in your branches to allow Odoo.sh to download them." msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:176 msgid "" "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 :ref:`Submodules ` of this " "documentation." msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:183 msgid "" "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." msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:188 msgid "" "To configure the deploy key for a private repository, proceed as follows:" msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:190 msgid "" "in the input, paste the SSH URL of your private sub-repository and click on " "*Add*," msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:192 msgid "e.g. *git@github.com:USERNAME/REPOSITORY.git*" msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:193 msgid "" "it can be another Git server than Github, such as Bitbucket, Gitlab or even " "your own self-hosted server" msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:196 msgid "copy the public key," msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:198 msgid "it should look like *ssh-rsa some...random...characters...here...==*" msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:200 msgid "" "in the settings of the private sub-repository, add the public key amongst " "the deploy keys." msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:202 msgid "" "Github.com: :menuselection:`Settings --> Deploy keys --> Add deploy key`" msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:203 msgid "Bitbucket.com: :menuselection:`Settings --> Access keys --> Add key`" msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:204 msgid "Gitlab.com: :menuselection:`Settings --> Repository --> Deploy Keys`" msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:205 msgid "" "Self-hosted: append the key to the git user’s authorized_keys file in its " ".ssh directory" msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:208 msgid "Storage Size" msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:210 msgid "This section shows the storage size used by your project." msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:215 msgid "Storage size is computed as follows:" msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:217 msgid "the size of the PostgreSQL database" msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:219 msgid "" "the size of the disk files available in your container: database filestore, " "sessions storage directory..." msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:222 msgid "" "In case you want to analyze disk usage, you can run the tool `ncdu " "`_ in your Web Shell." msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:225 msgid "" "Should your production database size grow to exceed what's provisioned in " "your subscription, it will automatically be synchronized with it." msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:229 msgid "Database Workers" msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:231 msgid "" "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." msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:239 msgid "" "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 " "`_." msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:245 msgid "Staging Branches" msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:247 msgid "" "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." msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:254 msgid "Activation" msgstr "활성화" #: ../../content/administration/odoo_sh/getting_started/settings.rst:256 msgid "" "Shows the status of the project's activation. You can change the project's " "activation code if needed." msgstr "" #: ../../content/administration/odoo_sh/getting_started/status.rst:8 msgid "" "The status page shows statistics regarding the servers your project uses. It" " includes the servers availability." msgstr "" #: ../../content/administration/odoo_sh/overview/introduction.rst:3 msgid "Introduction to Odoo.sh" msgstr "" #: ../../content/administration/odoo_sh/overview/introduction.rst:10 msgid "" "The documentation will help you go live with your Odoo.sh project in no " "time." msgstr "" #: ../../content/administration/upgrade.rst:7 msgid "" "An upgrade is the process of moving your database from an older version to a" " newer :doc:`supported version ` (e.g., Odoo " "14.0 to Odoo 16.0). Frequently upgrading is essential as each version comes " "with new and improved features, bug fixes, and security patches." msgstr "" #: ../../content/administration/upgrade.rst:15 msgid "" "The Rolling Release process allows Odoo Online customers to upgrade their " "database directly from a message prompt sent to the database administrator " "as soon as a new version is released. The invitation to upgrade is only sent" " if no issues are detected during the automatic tests." msgstr "" #: ../../content/administration/upgrade.rst:0 msgid "The upgrade message prompt on the top right of the database" msgstr "" #: ../../content/administration/upgrade.rst:22 msgid "" "It is strongly recommended to manually :ref:`test the upgrade first " "`. Clicking :guilabel:`I want to test first` redirects" " to `the database manager `_, where it " "is possible to request an upgraded test database and check it for any " "discrepancies." msgstr "" #: ../../content/administration/upgrade.rst:27 msgid "" "It is **not** recommended to click :guilabel:`Upgrade Now` without testing " "first, as it immediately triggers the live production database upgrade." msgstr "" #: ../../content/administration/upgrade.rst:30 msgid "" "If the Rolling Release process detects an issue with the upgrade, it will be" " deactivated until the issue is resolved." msgstr "" #: ../../content/administration/upgrade.rst:33 msgid "An upgrade does not cover:" msgstr "" #: ../../content/administration/upgrade.rst:35 msgid "Downgrading to a previous version of Odoo" msgstr "" #: ../../content/administration/upgrade.rst:36 msgid "" ":doc:`Switching editions ` (e.g., from Community to " "Enterprise)" msgstr "" #: ../../content/administration/upgrade.rst:37 msgid "" ":doc:`Changing hosting type ` " "(e.g., from on-premise to Odoo Online)" msgstr "" #: ../../content/administration/upgrade.rst:39 msgid "Migrating from another ERP to Odoo" msgstr "" #: ../../content/administration/upgrade.rst:42 msgid "" "If your database contains custom modules, it cannot be upgraded until a " "version of your custom modules is available for the target version of Odoo. " "For customers maintaining their own custom modules, we recommend to " "parallelize the process by :ref:`requesting an upgraded database " "` while also :doc:`upgrading the source code " "of your custom modules `." msgstr "" #: ../../content/administration/upgrade.rst:50 msgid "Upgrading in a nutshell" msgstr "" #: ../../content/administration/upgrade.rst:52 msgid "" "Request an upgraded test database (see :ref:`obtaining an upgraded test " "database `)." msgstr "" #: ../../content/administration/upgrade.rst:55 msgid "" "If applicable, upgrade the source code of your custom module to be " "compatible with the new version of Odoo (see " ":doc:`/developer/howtos/upgrade_custom_db`)." msgstr "" #: ../../content/administration/upgrade.rst:58 msgid "" "Thoroughly test the upgraded database (see :ref:`testing the new version of " "the database `)." msgstr "" #: ../../content/administration/upgrade.rst:61 msgid "" "Report any issue encountered during the testing to Odoo via the `support " "page `__." msgstr "" #: ../../content/administration/upgrade.rst:64 msgid "" "Once all issues are resolved and you are confident that the upgraded " "database can be used as your main database without any issues, plan the " "upgrade of your production database." msgstr "" #: ../../content/administration/upgrade.rst:67 msgid "" "Request the upgrade for the production database, rendering it unavailable " "for the time it takes to complete the process (see :ref:`upgrading the " "production database `)." msgstr "" #: ../../content/administration/upgrade.rst:70 msgid "" "Report any issue encountered during the upgrade to Odoo via the `support " "page `__." msgstr "" #: ../../content/administration/upgrade.rst:76 msgid "Obtaining an upgraded test database" msgstr "" #: ../../content/administration/upgrade.rst:78 msgid "" "The `Upgrade page `_ is the main platform for " "requesting an upgraded database. However, depending on the hosting type, you" " can upgrade from the command line (on-premise), the `Odoo Online database " "manager `_, or your `Odoo.sh project " "`_." msgstr "" #: ../../content/administration/upgrade.rst:84 msgid "" "The Upgrade platform follows the same `Privacy Policy " "`_ as the other Odoo.com services. Visit the " "`General Data Protection Regulation page `_ to " "learn more about how Odoo handles your data and privacy." msgstr "" #: ../../content/administration/upgrade.rst:92 msgid "" "Odoo Online databases can be manually upgraded via the `database manager " "`_." msgstr "" #: ../../content/administration/upgrade.rst:95 msgid "" "The database manager displays all databases associated with the user's " "account. Databases not on the most recent version of Odoo display an arrow " "in a circle icon next to their name, indicating that they can be upgraded." msgstr "" #: ../../content/administration/upgrade.rst:0 msgid "" "The database manager with an upgrade button next to the name of a database." msgstr "" #: ../../content/administration/upgrade.rst:102 msgid "" "Click the **arrow in a circle** icon to start the upgrade process. In the " "popup, fill in:" msgstr "" #: ../../content/administration/upgrade.rst:104 msgid "" "The **version** of Odoo you want to upgrade to, usually the latest version" msgstr "" #: ../../content/administration/upgrade.rst:105 msgid "" "The **email** address that should receive the link to the upgraded database" msgstr "" #: ../../content/administration/upgrade.rst:106 msgid "" "The :guilabel:`Purpose` of the upgrade, which is automatically set to " ":guilabel:`Test` for your first upgrade request" msgstr "" #: ../../content/administration/upgrade.rst:0 msgid "The \"Upgrade your database\" popup." msgstr "" #: ../../content/administration/upgrade.rst:112 msgid "" "The :guilabel:`Upgrade in progress` tag is displayed next to the database " "name until completion. Once the process succeeds, an email containing a link" " to the upgraded test database is sent to the address provided. The database" " can also be accessed from the database manager by clicking the dropdown " "arrow before the database name." msgstr "" #: ../../content/administration/upgrade.rst:0 msgid "Clicking the menu arrow displays the upgraded test database." msgstr "" #: ../../content/administration/upgrade.rst:122 msgid "" "Odoo.sh is integrated with the upgrade platform to simplify the upgrade " "process." msgstr "" #: ../../content/administration/upgrade.rst:0 msgid "Odoo.sh project and tabs" msgstr "" #: ../../content/administration/upgrade.rst:127 msgid "" "The **latest production daily automatic backup** is then sent to the " "`upgrade platform `_." msgstr "" #: ../../content/administration/upgrade.rst:130 msgid "" "Once the upgrade platform is done upgrading the backup and uploading it on " "the branch, it is put in a **special mode**: each time a **commit is " "pushed** on the branch, a **restore operation** of the upgraded backup and " "an **update of all the custom modules** occur. This allows you to test your " "custom modules on a pristine copy of the upgraded database. The log file of " "the upgrade process can be found in your newly upgraded staging build by " "going to :file:`~/logs/upgrade.log`." msgstr "" #: ../../content/administration/upgrade.rst:138 msgid "" "In databases where custom modules are installed, their source code must be " "up-to-date with the target version of Odoo before the upgrade can be " "performed. If there are none, the \"update on commit\" mode is skipped, the " "upgraded database is built as soon as it is transferred from the upgrade " "platform, and the upgrade mode is exited." msgstr "" #: ../../content/administration/upgrade.rst:143 msgid "" "Check out the :doc:`/developer/howtos/upgrade_custom_db` page for more " "information." msgstr "" #: ../../content/administration/upgrade.rst:145 #: ../../content/administration/upgrade.rst:341 msgid "On-premise" msgstr "" #: ../../content/administration/upgrade.rst:147 msgid "" "The standard upgrade process can be initiated by entering the following " "command line on the machine where the database is hosted:" msgstr "" #: ../../content/administration/upgrade.rst:154 msgid "" "The following command can be used to display the general help and the main " "commands:" msgstr "" #: ../../content/administration/upgrade.rst:160 msgid "" "An upgraded test database can also be requested via the `Upgrade page " "`_." msgstr "" #: ../../content/administration/upgrade.rst:164 msgid "" "In databases where custom modules are installed, their source code must be " "up-to-date with the target version of Odoo before the upgrade can be " "performed. Check out the :doc:`/developer/howtos/upgrade_custom_db` page for" " more information." msgstr "" #: ../../content/administration/upgrade.rst:169 msgid "" "For security reasons, only the person who submitted the upgrade request can " "download it." msgstr "" #: ../../content/administration/upgrade.rst:170 msgid "" "For storage reasons, the database's copy is submitted without a filestore to" " the upgrade server. Therefore, the upgraded database does not contain the " "production filestore." msgstr "" #: ../../content/administration/upgrade.rst:172 msgid "" "Before restoring the upgraded database, its filestore must be merged with " "the production filestore to be able to perform tests in the same conditions " "as it would be in the new version." msgstr "" #: ../../content/administration/upgrade.rst:175 msgid "The upgraded database contains:" msgstr "" #: ../../content/administration/upgrade.rst:177 msgid "A `dump.sql` file containing the upgraded database" msgstr "" #: ../../content/administration/upgrade.rst:178 msgid "" "A `filestore` folder containing files extracted from in-database records " "into attachments (if there are any) and new standard Odoo files from the " "targeted Odoo version (e.g., new images, icons, payment provider's logos, " "etc.). This is the folder that should be merged with the production " "filestore in order to get the full upgraded filestore." msgstr "" #: ../../content/administration/upgrade.rst:185 msgid "" "You can request multiple test databases if you wish to test an upgrade more " "than once." msgstr "" #: ../../content/administration/upgrade.rst:190 msgid "" "When an upgrade request is completed, an upgrade report is attached to the " "successful upgrade email, and it becomes available in the Discuss app for " "users who are part of the \"Administration / Settings\" group. This report " "provides important information about the changes introduced by the new " "version." msgstr "" "업그레이드 요청이 완료되면 업그레이드 성공 안내 이메일에 업그레이드 보고서가 첨부되며 \"관리/설정\" 그룹에 속한 사용자는 메일 및 " "채팅 앱에서 해당 보고서를 확인할 수 있습니다. 이 보고서에는 새 버전 도입으로 인한 변경 사항과 관련된 중요한 정보를 제공합니다." #: ../../content/administration/upgrade.rst:198 msgid "Testing the new version of the database" msgstr "" #: ../../content/administration/upgrade.rst:200 msgid "" "It is essential to spend some time testing the upgraded test database to " "ensure that you are not stuck in your day-to-day activities by a change in " "views, behavior, or an error message once the upgrade goes live." msgstr "" #: ../../content/administration/upgrade.rst:205 msgid "" "Test databases are neutralized, and some features are disabled to prevent " "them from impacting the production database:" msgstr "" #: ../../content/administration/upgrade.rst:208 msgid "Scheduled actions are disabled." msgstr "" #: ../../content/administration/upgrade.rst:209 msgid "" "Outgoing mail servers are disabled by archiving the existing ones and adding" " a fake one." msgstr "" #: ../../content/administration/upgrade.rst:210 msgid "" "Payment providers and delivery carriers are reset to the test environment." msgstr "" #: ../../content/administration/upgrade.rst:211 msgid "" "Bank synchronization is disabled. Should you want to test the " "synchronization, contact your bank synchronization provider to get sandbox " "credentials." msgstr "" #: ../../content/administration/upgrade.rst:214 msgid "" "Testing as many of your business flows as possible is strongly recommended " "to ensure they are working correctly and to get more familiar with the new " "version." msgstr "" #: ../../content/administration/upgrade.rst:217 msgid "Basic test checklist" msgstr "" #: ../../content/administration/upgrade.rst:219 msgid "" "Are there views that are deactivated in your test database but active in " "your production database?" msgstr "" #: ../../content/administration/upgrade.rst:221 msgid "Are your usual views still displayed correctly?" msgstr "" #: ../../content/administration/upgrade.rst:222 msgid "Are your reports (invoice, sales order, etc.) correctly generated?" msgstr "" #: ../../content/administration/upgrade.rst:223 msgid "Are your website pages working correctly?" msgstr "" #: ../../content/administration/upgrade.rst:224 msgid "" "Are you able to create and modify records? (sales orders, invoices, " "purchases, users, contacts, companies, etc.)" msgstr "" #: ../../content/administration/upgrade.rst:226 msgid "Are there any issues with your mail templates?" msgstr "" #: ../../content/administration/upgrade.rst:227 msgid "Are there any issues with saved translations?" msgstr "" #: ../../content/administration/upgrade.rst:228 msgid "Are your search filters still present?" msgstr "" #: ../../content/administration/upgrade.rst:229 msgid "Can you export your data?" msgstr "" #: ../../content/administration/upgrade.rst:233 msgid "" "Checking a random product in your product catalog and comparing its test and" " production data to verify everything is the same (product category, selling" " price, cost price, vendor, accounts, routes, etc.)." msgstr "" #: ../../content/administration/upgrade.rst:236 msgid "Buying this product (Purchase app)." msgstr "" #: ../../content/administration/upgrade.rst:237 msgid "Confirming the reception of this product (Inventory app)." msgstr "" #: ../../content/administration/upgrade.rst:238 msgid "" "Checking if the route to receive this product is the same in your production" " database (Inventory app)." msgstr "" #: ../../content/administration/upgrade.rst:240 msgid "Selling this product (Sales app) to a random customer." msgstr "" #: ../../content/administration/upgrade.rst:241 msgid "" "Opening your customer database (Contacts app), selecting a customer (or " "company), and checking its data." msgstr "" #: ../../content/administration/upgrade.rst:243 msgid "Shipping this product (Inventory app)." msgstr "" #: ../../content/administration/upgrade.rst:244 msgid "" "Checking if the route to ship this product is the same as in your production" " database (Inventory app)." msgstr "" #: ../../content/administration/upgrade.rst:246 msgid "Validating a customer invoice (Invoicing or Accounting app)." msgstr "" #: ../../content/administration/upgrade.rst:247 msgid "" "Crediting the invoice (issuing a credit note) and checking if it behaves as " "in your production database." msgstr "" #: ../../content/administration/upgrade.rst:249 msgid "Checking your reports' results (Accounting app)." msgstr "" #: ../../content/administration/upgrade.rst:250 msgid "" "Randomly checking your taxes, currencies, bank accounts, and fiscal year " "(Accounting app)." msgstr "" #: ../../content/administration/upgrade.rst:251 msgid "" "Making an online order (Website apps) from the product selection in your " "shop until the checkout process and checking if everything behaves as in " "your production database." msgstr "" #: ../../content/administration/upgrade.rst:254 msgid "" "This list is **not** exhaustive. Extend the example to your other apps based" " on your use of Odoo." msgstr "" #: ../../content/administration/upgrade.rst:256 msgid "" "If you face an issue while testing your upgraded test database, you can " "request the assistance of Odoo via the `support page " "`__ by selecting the option related " "to testing the upgrade. In any case, it is essential to report any problem " "encountered during the testing to fix it before upgrading your production " "database." msgstr "" "업그레이드된 테스트용 데이터베이스를 테스트하는 동안 문제가 발생하면 '고객 지원 페이지 " "`__에서 업그레이드 테스트와 관련된 옵션을 선택하여 Odoo에 " "지원 요청을 할 수 있습니다. 어떤 경우든 프로덕션 데이터베이스를 업그레이드하기 전에 테스트 중에 발생한 문제를 보고하여 문제를 해결하는" " 것이 중요합니다." #: ../../content/administration/upgrade.rst:261 msgid "" "You might encounter significant differences with standard views, features, " "fields, and models during testing. Those changes cannot be reverted on a " "case-by-case basis. However, if a change introduced by a new version breaks " "a customization, it is the responsibility of the maintainer of your custom " "module to make it compatible with the new version of Odoo." msgstr "" "테스트 중에 일반 화면, 기능, 필드 및 모델에 상당한 차이가 발생할 수 있습니다. 해당 변경 사항은 사례별로 되돌릴 수 없습니다. " "다만, 새 버전에서 도입된 변경 사항으로 인해 사용자 지정이 중단되는 경우, 사용자 지정 모듈의 유지 관리자의 책임 하에 사용자 지정 " "모듈을 새 버전의 Odoo와 호환되도록 합니다." #: ../../content/administration/upgrade.rst:267 msgid "Do not forget to test:" msgstr "" #: ../../content/administration/upgrade.rst:269 msgid "Integrations with external software (EDI, APIs, etc.)" msgstr "" #: ../../content/administration/upgrade.rst:270 msgid "" "Workflows between different apps (online sales with eCommerce, converting a " "lead all the way to a sales order, delivery of products, etc.)" msgstr "" #: ../../content/administration/upgrade.rst:272 msgid "Data exports" msgstr "" #: ../../content/administration/upgrade.rst:273 msgid "Automated actions" msgstr "자동화된 작업" #: ../../content/administration/upgrade.rst:274 msgid "" "Server actions in the action menu on form views, as well as by selecting " "multiple records on list views" msgstr "" #: ../../content/administration/upgrade.rst:280 msgid "Upgrading the production database" msgstr "" #: ../../content/administration/upgrade.rst:282 msgid "" "Once the :ref:`tests ` are completed and you are " "confident that the upgraded database can be used as your main database " "without any issues, it is time to plan the go-live day. It can be planned in" " coordination with Odoo's upgrade support analysts, reachable via the " "`support page `__." msgstr "" #: ../../content/administration/upgrade.rst:287 msgid "" "Your production database will be unavailable during its upgrade. Therefore, " "we recommend planning the upgrade at a time when the use of the database is " "minimal." msgstr "" #: ../../content/administration/upgrade.rst:290 msgid "" "As the standard upgrade scripts and your database are constantly evolving, " "it is also recommended to frequently request another upgraded test database " "to ensure that the upgrade process is still successful, especially if it " "takes a long time to finish. **Fully rehearsing the upgrade process the day " "before upgrading the production database is also recommended.**" msgstr "" "표준 업그레이드 스크립트 및 데이터베이스가 계속하여 발전하고 있으므로 업그레이드 프로세스가 성공적으로 완료될 수 있도록, 특히 완료하는 " "데 시간이 오래 걸리는 경우에는 업그레이드된 테스트 데이터베이스를 자주 요청하는 것이 좋습니다. **프로덕션 데이터베이스를 업그레이드하기" " 전날 업그레이드 프로세스를 충분히 테스트해보는 것도 좋습니다.**" #: ../../content/administration/upgrade.rst:296 msgid "Going into production without first testing may lead to:" msgstr "" #: ../../content/administration/upgrade.rst:298 msgid "Users failing to adjust to the changes and new features" msgstr "" #: ../../content/administration/upgrade.rst:299 msgid "" "Business interruptions (e.g., no longer having the possibility to validate " "an action)" msgstr "" #: ../../content/administration/upgrade.rst:300 msgid "" "Poor customer experience (e.g., an eCommerce website that does not work " "correctly)" msgstr "" #: ../../content/administration/upgrade.rst:302 msgid "" "The process of upgrading a production database is similar to upgrading a " "test database with a few exceptions." msgstr "" #: ../../content/administration/upgrade.rst:309 msgid "" "The process is similar to :ref:`obtaining an upgraded test database " "`, except for the purpose option, which must " "be set to :guilabel:`Production` instead of :guilabel:`Test`." msgstr "" #: ../../content/administration/upgrade.rst:314 msgid "" "Once the upgrade is requested, the database will be unavailable until the " "upgrade is finished. Once the process is completed, it is impossible to " "revert to the previous version." msgstr "" "업그레이드 요청 시 업그레이드가 완료될 때까지 데이터베이스를 사용할 수 없습니다. 프로세스가 완료되면 이전 버전으로 되돌릴 수 없습니다." #: ../../content/administration/upgrade.rst:320 msgid "" "The process is similar to :ref:`obtaining an upgraded test database " "` on the :guilabel:`Production` branch." msgstr "" #: ../../content/administration/upgrade.rst:0 msgid "View from the upgrade tab" msgstr "" #: ../../content/administration/upgrade.rst:326 msgid "" "The process is **triggered as soon as a new commit is made** on the branch. " "This allows the upgrade process to be synchronized with the deployment of " "the custom modules' upgraded source code. If there are no custom modules, " "the upgrade process is triggered immediately." msgstr "" "이 프로세스는 브랜치에 새로운 커밋이 생성되는 즉시 **작동**됩니다. 이렇게 하면 업그레이드 프로세스가 사용자 지정 모듈로 업그레이드된" " 소스 코드 배포와 동기화될 수 있습니다. 사용자 지정 모듈이 없는 경우에는 업그레이드 프로세스가 즉시 연계되어 작동됩니다." #: ../../content/administration/upgrade.rst:332 msgid "" "The database is unavailable throughout the process. If anything goes wrong, " "the platform automatically reverts the upgrade, as it would be for a regular" " update. In case of success, a backup of the database before the upgrade is " "created." msgstr "" "작업 전반에서 데이터베이스를 사용할 수 없습니다. 문제가 발생할 경우, 일반 업데이트와 마찬가지로 플랫폼에서 업그레이드를 자동으로 " "되돌립니다. 업그레이드가 성공하면 업그레이드 전 데이터베이스의 백업이 생성됩니다." #: ../../content/administration/upgrade.rst:336 msgid "" "The update of your custom modules must be successful to complete the entire " "upgrade process. Make sure the status of your staging upgrade is " ":guilabel:`successful` before trying it in production. More information on " "how to upgrade your custom modules can be found on " ":doc:`/developer/howtos/upgrade_custom_db`." msgstr "" "전체 업그레이드 프로세스를 완료하려면 커스텀 모듈의 업데이트가 성공해야 합니다. 프로덕션 환경에서 시도하기 전에 스테이지 업그레이드의 " "상태가 :guilabel:`성공`인지 확인하세요. 사용자 정의 모델을 업그레이드하는 자세한 방법은 " ":doc:`/developer/howtos/upgrade_custom_db`에서 확인하실 수 있습니다." #: ../../content/administration/upgrade.rst:343 msgid "" "The command to upgrade a database to production is similar to the one of " "upgrading a test database except for the argument `test`, which must be " "replaced by `production`:" msgstr "" "데이터베이스를 프로덕션으로 업그레이드하는 명령어는 테스트 데이터베이스를 업그레이드하는 명령어와 유사하며 반드시 `test` 인수를 " "`production`으로 대체해야 합니다." #: ../../content/administration/upgrade.rst:350 msgid "" "An upgraded production database can also be requested via the `Upgrade page " "`_. Once the database is uploaded, any " "modification to your production database will **not** be present on your " "upgraded database. This is why we recommend not using it during the upgrade " "process." msgstr "" "프로덕션 데이터베이스 업그레이드는 '업그레이드 페이지`_를 통해서도 요청할 수 있습니다." " 데이터베이스가 업로드되면 프로덕션 데이터베이스에 대한 수정 사항은 업그레이드된 데이터베이스에 나타나지 **않습니다**. 그렇기 때문에 " "업그레이드 프로세스 중에는 사용하지 않는 것이 좋습니다." #: ../../content/administration/upgrade.rst:357 msgid "" "When requesting an upgraded database for production purposes, the copy is " "submitted without a filestore. Therefore, the upgraded database filestore " "must be merged with the production filestore before deploying the new " "version." msgstr "" "프로덕션 목적으로 업그레이드된 데이터베이스를 요청할 경우 파일 저장소 없이 복사본이 제출됩니다. 따라서 새 버전을 배포하기 전에 " "업그레이드된 데이터베이스 파일 저장소를 프로덕션 파일 저장소와 병합해야 합니다." #: ../../content/administration/upgrade.rst:361 msgid "" "In case of an issue with your production database, you can request the " "assistance of Odoo via the `support page " "`__ by selecting the option " "related to the upgrade in production." msgstr "" #: ../../content/administration/upgrade.rst:369 msgid "Service-level agreement (SLA)" msgstr "서비스 수준 계약 (SLA : Service-level agreement)" #: ../../content/administration/upgrade.rst:371 msgid "" "With Odoo Enterprise, upgrading a database to the most recent version of " "Odoo is **free**, including any support required to rectify potential " "discrepancies in the upgraded database." msgstr "" #: ../../content/administration/upgrade.rst:374 msgid "" "Information about the upgrade services included in the Enterprise Licence is" " available in the :ref:`Odoo Enterprise Subscription Agreement `. " "However, this section clarifies what upgrade services you can expect." msgstr "" #: ../../content/administration/upgrade.rst:379 msgid "Upgrade services covered by the SLA" msgstr "" #: ../../content/administration/upgrade.rst:381 msgid "" "Databases hosted on Odoo's cloud platforms (Odoo Online and Odoo.sh) or " "self-hosted (On-Premise) can benefit from upgrade services at all times for:" msgstr "" #: ../../content/administration/upgrade.rst:384 msgid "the upgrade of all **standard applications**;" msgstr "" #: ../../content/administration/upgrade.rst:385 msgid "" "the upgrade of all **customizations created with the Studio app**, as long " "as Studio is still installed and the respective subscription is still " "active; and" msgstr "" #: ../../content/administration/upgrade.rst:387 msgid "" "the upgrade of all **developments and customizations covered by a " "maintenance of customizations subscription**." msgstr "" #: ../../content/administration/upgrade.rst:390 msgid "" "Upgrade services are limited to the technical conversion and adaptation of a" " database (standard modules and data) to make it compatible with the version" " targeted by the upgrade." msgstr "" #: ../../content/administration/upgrade.rst:394 msgid "Upgrade services not covered by the SLA" msgstr "" #: ../../content/administration/upgrade.rst:396 msgid "The following upgrade-related services are **not** included:" msgstr "" #: ../../content/administration/upgrade.rst:398 msgid "" "the **cleaning** of pre-existing data and configurations while upgrading;" msgstr "" #: ../../content/administration/upgrade.rst:399 msgid "" "the upgrade of **custom modules created in-house or by third parties**, " "including Odoo partners;" msgstr "" #: ../../content/administration/upgrade.rst:400 msgid "" "lines of **code added to standard modules**, i.e., customizations created " "outside the Studio app, code entered manually, and :ref:`automated actions " "using Python code `; and" msgstr "" #: ../../content/administration/upgrade.rst:403 msgid "**training** on using the upgraded version's features and workflows." msgstr "" #: ../../content/administration/upgrade.rst:406 msgid ":doc:`Odoo.sh documentation `" msgstr ":doc:`Odoo.sh 참고 문서 `" #: ../../content/administration/upgrade.rst:407 msgid ":doc:`Supported Odoo versions `" msgstr ":doc:`지원되는 Odoo 버전 `"