在后端和前端之间共享工作的最简单方法

发布于 2024-10-14 00:47:54 字数 534 浏览 1 评论 0原文

嘿大家, 我正在扩大我的团队,最近我在我的网站上添加了一名额外的前端工程师。我目前使用 django 来运行我的网站,但我的网站使用了很多插件,即:django-celery、django-mailer、django-notification 和 django-socialregistration。

让我描述一下我的情况:

  1. 他使用的是 Mac OS X,而我没有在 mac os X 上安装东西或在该平台上配置的经验
  2. 我相信让我的后端在他的计算机上运行可能有点麻烦,即我必须安装一堆插件(在 pip 或 easy_install 上不可用,因为它们是最新版本),我还对 django-socialregistration 进行了重大修改,我目前正在使用它,通过符号链接到我的 python 路径中的存储库中的修改后的代码
  3. 我试图研究像 pip 和 easy_install 这样的解决方案,但我无法让他们从 github 安装代码,

我认为最简单的方法是让我的后端在他的计算机上工作,然后他只需提交到存储库。我有什么想法可以让这变得简单吗?

Hey everyone,
I am expanding my team and I have recently added an additional front end engineer on my site. I am currently using django to run my site but my site is using a lot of plugins, namely: django-celery, django-mailer, django-notification, and django-socialregistration.

Let me describe my situation:

  1. He is using Mac OS X, and I have no experience in installing stuff on mac os X or configuration on that platform
  2. I believe that getting my backend to run on his computer might be somewhat troublesome, i.e. I have to install a bunch of plugins (which are not available on pip or easy_install as they are the latest version) and I have also made heavy modification to django-socialregistration which I am currently using by symlinking to the modified code in my repos in my python path
  3. I tried to look into solutions like pip and easy_install but I have not been able to get them to install code from github

I think the easiest way is to get my backend working on his computer and then he just commiting to the repos. Any ideas how I can make this easy?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(3

随梦而飞# 2024-10-21 00:47:54

另一个免费选项是使用 VirtualBox。我建议在其上安装与生产服务器相同的操作系统。然后,他在与实时站点相同的环境中进行开发,并且可以像您一样检查存储库。嘿,您可能想在自己的一端执行相同的操作 - 那么您的两个环境都是相同的,也与实时站点相同。

Another, free option, is to use VirtualBox. I would recommend installing the same OS on it as your production server. Then, he's developing in the same environment as the live site, and can just check into the repo the same as you. Hey, you may want to do the same on your end--then both of your environments are the same and also the same as the live site.

于我来说 2024-10-21 00:47:54

让他使用 VMWare Fusion 或 Parallels 在他的 Mac 上设置虚拟机,运行与您当前后端使用的操作系统相同的操作系统。如果他更喜欢使用 Mac 工具进行开发,他仍然可以通过共享目录将本地更改共享到虚拟机来实现这一点。

Get him to set up a virtual machine on his Mac, using VMWare Fusion or Parallels, running the same operating system that you currently use for your back end. If he prefers developing using Mac tools he can do still that by sharing his local changes to the virtual machine via a shared directory.

你的他你的她 2024-10-21 00:47:54

如果可能的话,另一种方法是在具有您熟悉的操作系统的计算机上设置测试/开发环境,然后在他的本地计算机上安装类似 Dropbox 的东西,在那里他可以开发前端代码,并在具有后端组件的其他环境。 Dropbox 会将他的本地更改同步到该测试环境,以便他运行代码。

这样,他就可以使用该环境来测试他的代码,您不需要在他的计算机上设置后端(或保持最新),并且您仍然可以获得相同的功能。

再说一次,如果这是一个选择的话。

An alternative, if that's possible, would be to set up a testing/development environment on a machine with an OS you're familiar with, then install something like Dropbox on his local machine where he can develop the frontend code, and install Dropbox on that other environment with the backend components. Dropbox would sync his local changes to that testing environment for him to run the code on.

That way, he would be able to use that environment to test his code, you wouldn't need to set up a backend on his machine (or keep it up to date) and you'd still be getting the same functionality.

Again, if that's an option.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文