与用户进行生产解决方案pipenv,是否可行? [英] pipenv on production workaround with user, is it viable?

查看:63
本文介绍了与用户进行生产解决方案pipenv,是否可行?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

当我尝试设置以下内容时,我一直遇到此问题 EC2.t2免费层上的pipenv可用于Django的生产.

I have been experiencing this issue here when I am trying to set pipenv on EC2.t2 free tier for production with Django.

在同一篇文章中列出的解决方案中,它说:

On the solution listed on that same post it says:

请务必注意,pipenv可能无法 由于点子冲突而在全球范围内安装.您可以安装 用户级的pipenv:

it is important to note that pipenv will likely not be able to be installed at the global level due to the pip conflict. You can install pipenv at the user level:

pip install --user pipenv

pip install --user pipenv

我的问题是,由于这是生产模式,以后会不会因为给我带来一些随机用户特权的软件包而给我带来麻烦?

My question is, since this is production mode, wouldn't this be bringing me problems later on since I am installing my packages with some random user's privileges?

有人在生产中使用过pipenv的视频吗?

Anyone has any video of using pipenv in production?

推荐答案

不,这通常不会引起任何问题.

No, this usually should not cause any problems.

您需要注意的是,将要运行已安装应用程序的用户具有这样做的权限.我认为哪个用户创建您的应用程序最终将驻留在其中的virtualenv并不重要(基本上是pipenv所控制的东西).

All you need to be taking care of is that the user that is to be running your installed application has permission to do so. I don't think that it matters much which user creates the virtualenv your application will ultimately reside in (which basically is what pipenv controls).

这篇关于与用户进行生产解决方案pipenv,是否可行?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆