Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MIX_ENV=prod mix ecto.migrations does not see all files #81

Closed
mvalitov opened this issue Apr 22, 2017 · 8 comments
Closed

MIX_ENV=prod mix ecto.migrations does not see all files #81

mvalitov opened this issue Apr 22, 2017 · 8 comments

Comments

@mvalitov
Copy link

mvalitov commented Apr 22, 2017

I ran into the problem that mix ecto.migrate and mix ecto.migrations does not see my last migration files in production mode. But sees them in mode dev

mars@ubuntu:~/temp_phoenix/my_balance$ mix ecto.migrations

Repo: MyBalance.Repo

  Status    Migration ID    Migration Name
--------------------------------------------------
  up        20170315204850  create_user
  up        20170319184713  create_session
  up        20170321195200  create_budget
  up        20170321200354  create_users_budgets
  up        20170322193636  add_name_to_budgets
  up        20170323200738  create_operation
  up        20170414202921  create_category
  up        20170414203307  add_category_id_to_operations
  up        20170416184614  add_confirm_token_to_users
  up        20170420204700  add_user_timestamp_to_operations
  up        20170421195002  create_invitation_code
  up        20170421214515  add_constraint_to_user_budget

mars@ubuntu:~/temp_phoenix/my_balance$ MIX_ENV=prod mix ecto.migrations

Repo: MyBalance.Repo

  Status    Migration ID    Migration Name
--------------------------------------------------
  up        20170315204850  create_user
  up        20170319184713  create_session
  up        20170321195200  create_budget
  up        20170321200354  create_users_budgets
  up        20170322193636  add_name_to_budgets
  up        20170323200738  create_operation
  up        20170414202921  create_category
  up        20170414203307  add_category_id_to_operations

I tried to execute MIX_ENV=prod mix ecto.drop and MIX_ENV=prod mix ecto.create && MIX_ENV=prod mix ecto.migrate, but this did not work.

What could be the reason?

versions: phoenix_ecto 3.2.3 , ecto 2.1.4

@josevalim
Copy link
Member

josevalim commented Apr 22, 2017 via email

@mvalitov
Copy link
Author

I'm afraid I can not. The fact is that on another computer this problem is not there, all migrations work correctly. The problem only occurs on this server

@josevalim
Copy link
Member

Without a mechanism to reproduce the error, I am afraid there isn't much we can do.

@mvalitov
Copy link
Author

Can we communicate in some other way so that I can provide you with temporary access to my server?

@josevalim
Copy link
Member

@mvalitov thanks for the offer but we have limited time to maintain projects and we cannot afford to use it for tracking issues on production servers. Sorry.

@mvalitov
Copy link
Author

Yes, I understand you. I suggested this only because I copied all the code to another server, I did not find the problem. Hence, and giving you access to the source code, we will not fix anything. Thank you for the time devoted to my problem. Apparently, I have no other options but to work on another server, or completely clean up and reinstall on the current server?

@josevalim
Copy link
Member

@mvalitov it seems to be the case. You can try yet a third server and see if the issue exists or not. If it does not, it is likely an issue with the first server unrelated to Ecto or Phoenix. FWIW, this is the first time I see such issue reported.

@mvalitov
Copy link
Author

Removal and a new installation on the current server solved the problem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants